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.

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/agents/reidbaker-agent/skills/code-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

The skill body is well-structured, actionable, and properly splits detail into one-level-deep reference files. It would reach the top tier with an explicit validation gate in the critique step and slightly tighter prose.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence without re-explaining basic concepts, with only minor instances of guidance that could be trimmed (e.g. the Core Principles restating what the workflow covers).

4 / 5

Actionability

Provides concrete, executable commands ('gh pr view', 'gh pr diff', 'git diff --staged') and points to vetted criteria files; minor gaps are delegated to reference files rather than spelled out inline.

4 / 5

Workflow Clarity

A clear five-step sequence is present with an explicit critique/refine step acting as a feedback loop ('Filter out or modify comments'), though the validation checkpoint is implicit rather than an explicit validate-then-proceed gate.

4 / 5

Progressive Disclosure

Content is well split across clearly signaled one-level-deep references (splitting_reviews.md, review_criteria.md, critique_rules.md, split_diff.py) with a concise overview body; navigation is easy with only minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

78%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.

The description is specific, includes a clear 'Use when' trigger, and occupies a distinct niche. It is slightly generic in trigger phrasing and could add synonyms to reach the top level.

DimensionReasoningScore

Specificity

Names the domain (code review of pull requests or local changes) and several concrete actions ('generation, critique, synthesis'), giving good coverage with only minor gaps compared to the comprehensive 5-anchor.

4 / 5

Completeness

Clearly answers both 'what' (multi-step iterative review with generation/critique/synthesis) and 'when' ('Use when you need to review code changes thoroughly'), though the trigger could be slightly more specific.

4 / 5

Trigger Term Quality

Includes natural terms a user would say ('review code changes', 'pull requests', 'local code changes') with good coverage, though synonyms like 'diffs' or 'PRs' are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (multi-step code review of PR/local changes) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

20

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.