CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

qodo-review

Review local changes with Qodo during substantive coding milestones and before a PR or completed-work handoff. Use light background checkpoints while coding, collect and assess findings with session context, and run a final review before handing off. Also use for "review my local diff", "pre-PR review", or "run qodo review". Use qodo-review-resolver for findings already posted on a PR.

Quality

86%

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

67%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 body delivers genuinely executable guidance — guarded shell pipelines, exit-code semantics, and explicit validate-fix-rereview loops with bounded recovery — and its reference bundle is well-structured with real, one-level-deep files. Its main weakness is token efficiency: depth-selection policy is repeated across several sections and substantial material that belongs in reference files is inlined, making the document far longer than its actionable core requires.

Suggestions

Consolidate the depth-selection policy (fast/auto/deep criteria) into a single authoritative section; it is currently restated in 'Choose when and how deeply to review', 'Checkpoints and final handoff', 'Submit and collect', and 'Configuration'.

Move the runtime compatibility gate's update-route detail and the async collection internals (polling loop script, retry/exit-code mechanics) into reference files like the existing windows-shells.md pattern, keeping only the decision rules in SKILL.md.

Break the dense multi-clause policy sentences (e.g., in 'Checkpoints and final handoff' and 'Prepare a PR handoff') into short imperative rules or a checklist so each rule is scannable and independently enforceable.

DimensionReasoningScore

Conciseness

The body is domain-specific with almost no explanation of concepts Claude already knows, but at ~485 lines it is noticeably overlong: depth-selection policy is restated in "Choose when and how deeply to review", "Checkpoints and final handoff", "Submit and collect", and "Configuration", and sections like the runtime compatibility gate are dense run-on policy sentences that could be substantially tightened. Not score 2 because there is little true padding or generic explanation; not score 4 because the repetition and density mean real tightening is possible throughout.

3 / 5

Actionability

The skill provides fully worked shell snippets — the guarded async submission pipeline with jq validation, the mktemp/trap status-polling loop, an exit-code decision table, and a concrete JSON context example — plus specific commands like `qodo read whoami --json --skill qodo-review --skill-version 1.10.15`. Not score 5: the examples are explicitly illustrative ("Confirm the exact flags with `qodo review --help`"), the merge-base line needs "substitute the intended target", and MCP arguments are deferred to the live schema, so they are not copy-paste ready across common cases. Not score 3: the code given is real and executable with error handling, not pseudocode.

4 / 5

Workflow Clarity

The workflow has explicit validation checkpoints and feedback loops: bounded recovery with exit-code classification and `retry_after` handling, digest/byte-count verification for result chunks, "Batch authorized fixes, verify them, then re-review changed work", and the stop-an-unproductive-loop rule. Not score 5: the end-to-end sequence is fragmented across roughly fifteen topic sections (e.g., "Prepare a PR handoff" precedes "Instructions", the runtime gate follows "Execution"), so the reader must synthesize the order themselves; not score 3 because validation for the risky steps is present and explicit.

4 / 5

Progressive Disclosure

All eight bundle files referenced in the body exist (skill-updates.md, windows-shells.md, windows-launcher.md, review-turn-context.md with its #cli-examples anchor, connected-progress.md, finding-results.md, context-delivery.md, local-triage.md), are one level deep with no nested reference chains, and are clearly signaled at point of need. Not score 5: SKILL.md itself is a ~485-line exhaustive policy document rather than a lean overview — the runtime-update gate, async collection internals, and context field semantics are prime candidates to move into reference files.

4 / 5

Total

15

/

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.

The description is a strong example: concrete third-person actions covering the whole workflow, explicit quoted trigger phrases, both what and when clearly answered, and explicit de-confliction against the sibling PR-resolver skill. It is information-dense without padding.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering the skill's full lifecycle: "Review local changes with Qodo", "Use light background checkpoints while coding", "collect and assess findings with session context", and "run a final review before handing off", all in third person. Coverage is comprehensive rather than 1-2 actions (score 3) or having minor gaps (score 4); each capability of the workflow is named.

5 / 5

Completeness

It explicitly answers both questions: the 'what' is the concrete review workflow (checkpoints, collect and assess findings, final review) and the 'when' is stated twice — "during substantive coding milestones and before a PR or completed-work handoff" and the quoted trigger phrases. This matches the score-5 anchor of both what and when with concrete trigger phrases; score 4 would require the 'when' to be less explicit.

5 / 5

Trigger Term Quality

It includes explicit natural trigger phrases a user would actually say — "review my local diff", "pre-PR review", or "run qodo review" — plus milestone/handoff wording. Not score 4: no natural variants for this domain are conspicuously missing; the quoted phrases cover the colloquial ways users would request this skill.

5 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (Qodo local-change review before handoff) and explicitly disambiguates the sibling skill: "Use qodo-review-resolver for findings already posted on a PR". Tool-specific naming plus explicit routing guidance means minimal conflict risk, matching the score-5 anchor; score 4 would imply unaddressed overlap with a closely related skill.

5 / 5

Total

20

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

qodo-ai/qodo-skills

Path

skills/qodo-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.