CtrlK
BlogDocsLog inGet started
Tessl Logo

change-review

Use when reviewing a set of changes before they merge in a Repowise-indexed repository, a PR, a branch diff, or the working-tree changes you just made. Activates for "review this PR", "is this safe to merge", "what is the blast radius of these changes", or "did I miss anything".

69

Quality

84%

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

82%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-structured, actionable skill body that leads Claude through a concrete review workflow with executable MCP and CLI commands and honest treatment of tool gaps. The main room for improvement is tightening some directive-field prose and making a few validation checkpoints more explicit.

DimensionReasoningScore

Conciseness

The body is dense and operational, assuming Claude knows git/diff concepts and avoiding concept padding, but some prose around directive fields could be tightened, matching the 'efficient; minor instances of over-explanation' anchor.

4 / 5

Actionability

It provides concrete, copy-pasteable invocations (get_change_risk(revspec="main..HEAD"), get_risk(targets=..., changed_files=...), gh pr diff, git diff --name-only main...HEAD, repowise impacted-tests <revspec> | xargs pytest) covering the common cases.

5 / 5

Workflow Clarity

A clear ordered sequence (score the whole change → drill per-file → go deeper → get the diff → write the review → error handling) with checkpoints like 'read directive first' and the warning-field caveat; this is read-only review so the destructive-cap does not apply, but a couple of checkpoints are implicit rather than explicit.

4 / 5

Progressive Disclosure

The skill is a single well-organized file with clear section headers and no nested references (no bundle files exist), but at ~108 lines it exceeds the under-50-line simple-skill exception that would auto-score 5, so it sits at good structure with minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

86%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 that pairs an explicit Use-when clause with four natural trigger phrases and a well-scoped Repowise context. Its only weakness is capability specificity: it states one action (reviewing) across contexts rather than enumerating several concrete actions.

DimensionReasoningScore

Specificity

The description names the domain ('reviewing a set of changes before they merge') and several input contexts (PR, branch diff, working tree), but explicitly states only one concrete action — reviewing — rather than listing several specific actions, matching the anchor that names the domain with 1-2 actions.

3 / 5

Completeness

It explicitly answers both what (reviewing changes before merge) and when (Use when... + concrete trigger phrases), matching the anchor for clearly and explicitly answering both with concrete triggers.

5 / 5

Trigger Term Quality

It lists four natural phrases users would actually say ('review this PR', 'is this safe to merge', 'what is the blast radius of these changes', 'did I miss anything'), giving comprehensive coverage of natural trigger terms.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (Repowise-indexed change review) with distinct triggers, though 'did I miss anything' is generic enough to carry minor overlap risk with general code-review skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
repowise-dev/repowise
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.