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".

97

Quality

96%

Does it follow best practices?

Impact

Pending

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 use of quoted trigger phrases makes it very clear when this skill should be selected.

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

92%

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

This is a strong, well-crafted skill that provides clear, actionable guidance for PR cleanup with appropriate safety guardrails. The workflow is well-sequenced with explicit verification steps for destructive history rewriting. The only minor weakness is that all content lives in a single file, though the overall length is reasonable enough that this is a minor concern.

DimensionReasoningScore

Conciseness

Every section is lean and purposeful. No unnecessary explanations of what PRs are or how git works. Assumes Claude knows git, gh CLI, and PR workflows. Each bullet and code block earns its place.

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 and reviewer guidance bullets are specific and concrete rather than vague.

3 / 3

Workflow Clarity

The 5-step workflow is clearly sequenced with an explicit plan-before-act step. The history cleanup section includes a verification feedback loop (compare tree hashes, check diff stat, do not push if tree changed). The guardrails section adds safety constraints for destructive operations.

3 / 3

Progressive Disclosure

The content is well-organized into logical sections (Workflow, History Cleanup, Reviewer Guidance, Guardrails), but everything is inline in a single file. For a skill of this complexity, separating detailed commit grouping strategies or reviewer guidance templates into referenced files could improve navigation, though the current length is manageable.

2 / 3

Total

11

/

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.