CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-draft-summary

Create the required PR-ready summary block, branch suggestion, title, and draft description for ioredis. Must be used before the final response whenever the actual task diff includes runtime code, tests, examples, build/test configuration, or docs with behavior impact, regardless of perceived change size. Skip only when no eligible files changed, every change is repo-meta or docs-only without behavior impact, the task is conversation-only, or the user explicitly opts out.

72

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, highly actionable skill body: exact commands, deterministic fallback logic, and a complete output template with well-organized sections. The only improvements are removing the repeated skip-condition restatements and adding a lightweight self-check on the emitted PR block.

DimensionReasoningScore

Conciseness

The body is lean and imperative, adding only non-obvious notes (e.g. untracked files because "`--stat` omits them", never using a feature branch's upstream as the PR base), but the skip conditions are restated in the Close-out Gate, the Workflow, and the Output Format intro, which could be trimmed.

4 / 5

Actionability

Every step is executable: exact git commands with flags, a deterministic BASE_REF fallback chain (upstream/main → origin/main → main) with merge-base computation, concrete branch-naming patterns, and a copy-paste output template covering the common cases.

5 / 5

Workflow Clarity

The nine steps are clearly sequenced with real checkpoints (compute BASE_REF/BASE_COMMIT first for reuse, empty-combined-diff early exit, "Do not block if the issue cannot be fetched"), but there is no validation of the emitted block itself and the change-type classification steps rely on judgment, leaving minor gaps versus the explicit-feedback-loop anchor.

4 / 5

Progressive Disclosure

The ~60-line body has well-organized sections (Purpose, Close-out Gate, Inputs, Workflow, Output Format), no bundle files are needed, and nothing is inlined that clearly belongs in a separate file, so the structure fully serves navigation.

5 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete actions, explicit what/when triggers, defined skip cases, and a clear ioredis-scoped niche. Its only weakness is slightly incomplete natural-phrase coverage (no spelled-out "pull request" or common synonyms).

DimensionReasoningScore

Specificity

The description lists four concrete actions ("PR-ready summary block, branch suggestion, title, and draft description") that comprehensively cover the skill's output, matching the multiple-specific-actions anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

It explicitly answers both what ("Create the required PR-ready summary block, branch suggestion, title, and draft description") and when ("Must be used before the final response whenever the actual task diff includes runtime code, tests, examples, build/test configuration, or docs with behavior impact") with concrete triggers, plus explicit skip conditions.

5 / 5

Trigger Term Quality

Natural terms like "PR-ready summary", "branch suggestion", "title", "draft description", "runtime code", "tests", and "diff" give good coverage, but the spelled-out phrase "pull request" and common user phrasings like "PR description" or "summarize my changes" are missing, placing it just below the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

Scoping to "for ioredis" with a diff-content-based trigger carves a clear niche with minimal conflict risk; only trivial overlap with generic commit-message or PR-helper skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
redis/ioredis
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.