CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

Quality

87%

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 well-crafted, lean skill body with concrete commands, a sensible commit grouping, and strong safety validation around destructive history rewriting. Its only gaps are the missing rewrite commands themselves and an implicit rather than explicit failure-recovery step.

DimensionReasoningScore

Conciseness

The body is lean and directive with zero padding — it never explains concepts Claude already knows, and every line ('Never hide meaningful behavior changes inside cleanup') earns its place.

5 / 5

Actionability

Provides concrete, executable gh/git commands and a specific commit-grouping order, but requires placeholder substitution (<PR>, <headRefName>) and omits the actual history-rewrite commands (rebase/squash).

4 / 5

Workflow Clarity

Clear five-step sequence with explicit validation for a destructive operation — capturing ORIGINAL_TREE before rewriting and comparing tree hashes after, with a 'Do not push if the tree changed unintentionally' checkpoint. Falls short of 5 only because there is no explicit recovery loop when the tree check fails.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed; the ~54-line body is organized into clear sections (Workflow, History Cleanup, Reviewer Guidance, Guardrails), which satisfies the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

83%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: it states concrete capabilities in third person and pairs them with explicit, natural 'Use for' trigger phrases. The only weaknesses are mild abstraction in 'cleaning noisy history' and a few missing trigger synonyms.

DimensionReasoningScore

Specificity

Names the domain (PR review preparation) and lists several concrete actions — 'cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior' — with only minor abstraction ('cleaning noisy history' doesn't specify squash/rebase).

4 / 5

Completeness

Explicitly answers both what (prepare PRs for review via three named actions) and when (a 'Use for' clause with four concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural quoted trigger phrases users would actually say ('make this easy to review', 'tidy this PR', 'clean up commits', 'annotate the diff'), but misses a few common synonyms like 'squash commits' or 'polish this PR'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear PR-reviewability niche with distinct triggers, but has minor overlap risk with generic code-review or commit-message skills (e.g., 'clean up commits').

4 / 5

Total

17

/

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

cursor/plugins

Path

cursor-team-kit/skills/make-pr-easy-to-review/SKILL.md

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.