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

79%

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 ./packages/qodo/skills/qodo-review/SKILL.md
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 highly actionable, well-validated operational guidance with genuine feedback loops and a well-structured one-level-deep reference bundle. Its main costs are repetition and sheer size: ~485 lines with the depth policy restated three times and long policy blocks (runtime gate, async costs) inlined that would fit better as reference files, and a scattered section order that makes the end-to-end flow harder to follow than its validation quality deserves.

Suggestions

Consolidate the depth-selection policy into a single section and have 'Submit and collect with --async' and 'Configuration' reference it instead of restating it, cutting the most visible repetition.

Move the 'Runtime compatibility gate' and the async 'What it costs' details into files under references/ (like the existing windows-shells/local-triage pattern), leaving a two-line summary and link in SKILL.md.

Reorder sections into a linear flow (prerequisites → depth choice → preflight → submit → collect → assess → act → recover) so 'Quick start' and the execution rules appear before the deep policy material they set up.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and most tokens carry non-inferable operational policy, but at ~485 lines it is repetitive and could be tightened: the depth-selection policy is restated in three places ('Choose when and how deeply to review', 'Submit and collect with --async', 'Configuration'), the runtime compatibility gate is a dense 20-line run-on block, and push/collect guardrails recur across sections. It sits between anchors 2 and 3 — inefficient in spots but not padded with unnecessary explanations — so anchor 3 with clear tightening opportunities is the best fit.

3 / 5

Actionability

Provides copy-paste-ready shell for the async submit and collect loop (jq guards, mktemp, traps), an exit-code table with explicit actions, a concrete session-context JSON schema, specific error codes (closed_preview, MT-REPO-NO-CREDENTIAL), and exact commands (qodo --version, git merge-base HEAD origin/main). The 'examples are illustrative — confirm with --help' hedge is explicitly justified by CLI version variance, and minor gaps remain in the connected-progress and MCP paths, placing it just below anchor 5's fully-executable-everywhere bar.

4 / 5

Workflow Clarity

Explicit validation checkpoints abound (exit-code table prescribing actions, 'recheck findings against current code', 'Pending, failed, partial or superseded review is not clean') and feedback loops are thorough (fix → verify → re-review; bounded recovery with 'retry once... stop on further failure'). However the sequence is scattered rather than linear: 'Quick start' appears mid-document after the runtime gate, and execution guidance is split across 'Choose execution for the selected review', 'Execution', and 'Submit and collect', requiring the reader to assemble the flow. This lands between anchors 4 and 5 — validation is anchor-5 quality but organization is anchor-4.

4 / 5

Progressive Disclosure

All 8 bundle files in references/ are real, clearly signaled with descriptive link text and stated purpose ([Session context], [field guide], [connected progress], [shell guidance]), and one level deep — they link back to SKILL.md rather than nesting further. The weakness is that the 485-line body inlines substantial material that could live in references (the runtime compatibility gate, the async 'What it costs' details, and connected-progress canonical rules duplicated alongside their own reference file), which is more than the 'minor organization gaps' of anchor 4 but does not reach anchor 3's 'content that should be separate is inline' as the dominant characterization.

4 / 5

Total

15

/

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, gives explicit 'when' guidance with natural quoted trigger phrases, and cleanly boundaries itself against the related qodo-review-resolver skill. Its only weaknesses are a few missing natural trigger variations and capability details (fix/dismissal flow) left to the body.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'use light background checkpoints while coding', 'collect and assess findings with session context', 'run a final review before handing off' — with minor gaps (e.g., applying/dismissing findings is not surfaced). It goes beyond the 1-2 actions of anchor 3 but is not the comprehensive coverage of anchor 5.

4 / 5

Completeness

Explicitly answers both 'what' (review local changes, run checkpoints, collect and assess findings, final review before handoff) and 'when' with concrete trigger phrases ('during substantive coding milestones and before a PR or completed-work handoff', 'Also use for "review my local diff", "pre-PR review", or "run qodo review"'). This matches the anchor-5 pattern of concrete trigger phrases for both questions.

5 / 5

Trigger Term Quality

Includes natural quoted trigger phrases users would actually say: "review my local diff", "pre-PR review", "run qodo review", plus 'before a PR or completed-work handoff'. A few common variations (e.g., "review my changes", "check my work before pushing") are missing, so it falls short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The explicit routing boundary — 'Use qodo-review-resolver for findings already posted on a PR' — establishes a clear niche and disambiguates the sibling skill. Minor overlap risk remains with generic code-review skills for phrases like 'review my local diff', keeping it below anchor 5's minimal conflict risk.

4 / 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.

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

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