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

75

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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 concise, well-structured body that provides executable git commands and, importantly, explicit validation for the destructive history-rewrite operation. It is slightly short of fully copy-paste-ready actionability and an explicit fix-retry feedback loop, landing at the high end on most dimensions.

DimensionReasoningScore

Conciseness

Lean ~60-line body with no padding or explanation of git/PR concepts Claude already knows; every section earns its place and assumes Claude's competence.

5 / 5

Actionability

Provides concrete, executable bash (gh pr view, git rev-parse, git diff --stat) with PR-specific placeholders, but the Reviewer Guidance section is instructional rather than command-backed, leaving minor gaps.

4 / 5

Workflow Clarity

Clear numbered workflow plus an explicit destructive-operation validation checkpoint (capture ORIGINAL_TREE, compare trees after rewrite, 'Do not push if the tree changed unintentionally'); the recovery path on mismatch is stated as 'do not push' rather than a fix-and-retry loop, so it sits just below the top anchor.

4 / 5

Progressive Disclosure

Well-organized into clear sections (Workflow, History Cleanup, Reviewer Guidance, Guardrails) with no need for external references; content is appropriately self-contained and easy to navigate.

5 / 5

Total

18

/

20

Passed

Description

100%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, well-constructed description that states concrete capabilities, gives explicit 'Use for' trigger guidance with natural phrasings, and occupies a distinct niche. It hits the top anchor on all four dimensions.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both 'what' (prepare PRs for review by...) and 'when' (Use for...) with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural phrases users would actually say — 'make this easy to review', 'tidy this PR', 'clean up commits', 'annotate the diff' — covering multiple synonymous trigger phrasings.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (PR review preparation) with distinct triggers unlikely to fire for unrelated skills; minimal conflict risk.

5 / 5

Total

20

/

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.

Validation16 / 16 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.