CtrlK
BlogDocsLog inGet started
Tessl Logo

make-pr-easy-to-review

Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff".

80

Quality

100%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Discovery

100%

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

This is an excellent skill description that concisely communicates specific capabilities, provides natural trigger phrases users would actually say, and clearly delineates its scope. The 'without changing code behavior' qualifier is a smart addition that helps distinguish this from code refactoring skills. The description uses proper third-person voice and is well-structured.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'cleaning noisy history', 'improving PR descriptions', and 'adding reviewer guidance without changing code behavior'. These are distinct, actionable capabilities.

3 / 3

Completeness

Clearly answers both what ('cleaning noisy history, improving PR descriptions, adding reviewer guidance') and when ('Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff"') with explicit trigger phrases.

3 / 3

Trigger Term Quality

Includes highly natural trigger phrases users would actually say: 'make this easy to review', 'tidy this PR', 'clean up commits', 'annotate the diff'. These cover common variations of how users would request this functionality.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche around PR review preparation and commit cleanup. The explicit constraint 'without changing code behavior' further distinguishes it from code refactoring or general git skills. The trigger terms are specific to PR tidying rather than general git operations.

3 / 3

Total

12

/

12

Passed

Implementation

100%

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

This is a well-crafted skill that is concise, actionable, and clearly structured. It provides executable commands with explicit validation checkpoints for the destructive operation of history rewriting, and the guardrails section appropriately bounds the skill's scope. The commit grouping heuristic and reviewer guidance items add genuine value beyond what Claude would infer on its own.

DimensionReasoningScore

Conciseness

Every section is lean and purposeful. No unnecessary explanations of what PRs are, how git works, or why reviewability matters. The skill assumes Claude knows git, gh CLI, and PR workflows, and only provides the specific patterns and constraints needed.

3 / 3

Actionability

Provides executable bash commands for fetching PR info, capturing the original tree hash, and verifying content identity after rewriting. The commit grouping order is concrete and specific. The reviewer guidance section gives specific, actionable items rather than vague advice.

3 / 3

Workflow Clarity

The workflow is clearly sequenced (resolve → inspect → identify → propose plan → apply → verify). The history cleanup section has an explicit validation checkpoint (tree hash comparison before/after) with a clear 'do not push if tree changed' guardrail, forming a proper feedback loop for a destructive operation.

3 / 3

Progressive Disclosure

For a skill of this size (~50 lines of meaningful content) with no need for external references, the content is well-organized into logical sections (Workflow, History Cleanup, Reviewer Guidance, Guardrails) that are easy to scan and navigate. No bundle files are needed.

3 / 3

Total

12

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
cursor/plugins
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.