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

This is a highly actionable, defensively thorough skill: concrete commands, explicit validation checkpoints, bounded recovery, and a well-structured one-level reference bundle. Its main weakness is token efficiency — the body is roughly twice as long as it needs to be due to policy restated across sections and dense multi-clause prose.

Suggestions

Consolidate the depth-selection policy, which is currently stated in four places (the 'Choose when and how deeply to review' section, 'Checkpoints and final handoff', 'Configuration', and 'Guardrails'), into one canonical section referenced from the others.

Move the runtime compatibility gate and 1.x→2.x migration detail (currently ~20 dense lines) into a reference file, keeping a short gate summary plus link in the body.

Break the long multi-clause policy sentences into short imperative rules so each rule can be read once instead of re-parsed.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and carries high information density per line, but it runs ~490 lines with the depth-selection policy restated in four places (the selection table, checkpoints, Configuration, and Guardrails) and long multi-clause sentences ('Only when the runtime needs an update, before any update check/change, test whether QODO_UPDATE_BASE_URL is set; never print its value') that require re-reading. Not 2 because the problem is repetition and density, not fluff or padding.

3 / 5

Actionability

Provides concrete, executable artifacts: a version probe, a provenance-stamped `qodo read whoami` call, a fully guarded async-submission script with jq checks, a trap-based polling loop with an exit-code table, and a session-context JSON example. Not 5 because the examples are explicitly labeled 'illustrative' with a 'Confirm the exact flags with `qodo review --help`' caveat, so they are not guaranteed copy-paste ready.

4 / 5

Workflow Clarity

The lifecycle is well sequenced with explicit validation gates (runtime version probe, auth check, merge-base SHA resolution, digest/byte-count verification, exit-code handling) and genuine feedback loops (fix → verify → re-review, bounded recovery with retry limits). Not 5 because the ordering scatters the flow — 'Choose the execution path' and 'Choose execution for the selected review' overlap, and Quick start appears mid-document after the runtime gate.

4 / 5

Progressive Disclosure

All eight referenced files (skill-updates, windows-shells, windows-launcher, review-turn-context, connected-progress, finding-results, context-delivery, local-triage) exist, are one level deep, and are well-signaled with descriptive link text at the point of need; the `#cli-examples` anchor is real. Not 5 because the body inlines substantial dense policy — the runtime compatibility gate, 1.x→2.x migration detail, and async cost notes — that belongs in reference files, making the overview itself long.

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 timing guidance, and includes natural quoted trigger phrases. Its only weaknesses are minor — a few missing trigger synonyms and slight overlap risk with generic review requests.

DimensionReasoningScore

Specificity

Quotes several concrete actions — 'Use light background checkpoints while coding, collect and assess findings with session context, and run a final review before handing off' — covering the full review lifecycle. Not 5 because it stops short of the finding-disposition actions (fix/dismiss/investigate) that the skill actually performs.

4 / 5

Completeness

Explicitly answers both what ('Review local changes with Qodo... collect and assess findings with session context, and run a final review before handing off') and when ('during substantive coding milestones and before a PR or completed-work handoff', plus quoted trigger phrases). This matches the anchor-5 example structure with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would actually say: 'review my local diff', 'pre-PR review', and 'run qodo review'. Not 5 because common variations like 'code review my changes' or 'review before committing' are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche — Qodo local review — and it explicitly disambiguates the closest sibling skill ('Use qodo-review-resolver for findings already posted on a PR'). Not 5 because generic review requests like 'review my local diff' could also plausibly match other code-review skills, leaving minor overlap 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

codex-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.