CtrlK
BlogDocsLog inGet started
Tessl Logo

code-review

Performs a comprehensive, multi-step code review of pull requests or local code changes, using iterative refinement (generation, critique, synthesis) to ensure high-quality, actionable feedback. Use when you need to review code changes thoroughly.

72

Quality

88%

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

92%

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

A high-quality, actionable, and concise procedural skill body with a clear sequenced workflow and a real critique feedback loop. The one weakness is progressive disclosure: one reference file is bundled but never surfaced from the body.

Suggestions

Add a link to references/reviewing_tests.md (e.g., in Step 3 criteria or Step 2) so the bundled test-review guidance is discoverable rather than orphaned.

Optionally reference scripts/split_diff.py from Step 1 or 2 if it is intended for subdividing large diffs, so users know the helper exists.

DimensionReasoningScore

Conciseness

The body is lean and procedural — concrete commands, bulleted criteria, and terse directives like 'CRITICAL: Do not add comments...' — assuming Claude's competence without explaining what a PR or diff is; the only mild padding is the persona preamble.

3 / 3

Actionability

Provides fully executable commands (gh pr view/diff, git status/diff/log) and concrete output structure (File, Line, Severity, Body, Suggestion) with specific, copy-ready rules such as anchoring comments to lines beginning with '+' or '-'.

3 / 3

Workflow Clarity

Five steps are clearly sequenced (Gather → Context → Generate → Critique/Refine → Synthesis) with a genuine self-critique feedback loop and explicit gating rules, satisfying the anchor for a clear sequence with feedback loops.

3 / 3

Progressive Disclosure

SKILL.md is a well-signaled overview with one-level-deep references to real files (splitting_reviews.md, review_criteria.md, critique_rules.md), but reviewing_tests.md exists in references/ and is never linked from the body, leaving an orphaned file and a minor navigation gap.

2 / 3

Total

11

/

12

Passed

Description

85%

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, mostly precise description that clearly states both capability and an explicit use-trigger, with concrete phases named. The only gap is limited variation in trigger-term coverage.

Suggestions

Broaden trigger terms to match how users actually ask, e.g. add 'review my PR,' 'review a diff,' or 'review staged/committed changes' to the 'Use when...' clause.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and phases — 'comprehensive, multi-step code review,' 'iterative refinement (generation, critique, synthesis),' and 'actionable feedback' — matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ('Performs a comprehensive, multi-step code review...') and when via an explicit 'Use when you need to review code changes thoroughly' trigger clause.

3 / 3

Trigger Term Quality

Includes natural terms like 'code review,' 'pull requests,' and 'review code changes,' but misses common variations a user might say such as 'review my PR,' 'review a diff,' or 'review staged changes,' so coverage is incomplete.

2 / 3

Distinctiveness Conflict Risk

Scoped to 'pull requests or local code changes' with a distinctive iterative-refinement framing, giving it a clear niche unlikely to trigger for the wrong skill.

3 / 3

Total

11

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository
flutter/agent-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.