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

81%

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 is exceptionally actionable and validation-rich, with executable scripts, explicit error handling, and well-managed one-level-deep references. Its weaknesses are redundancy and density: key policies are repeated across sections, long multi-clause sentences demand rereading, and section order doesn't follow the execution timeline.

Suggestions

Consolidate the depth-selection policy (--fast/--deep/auto) into a single section and cross-reference it from 'Checkpoints and final handoff' and 'Configuration' instead of restating it three times.

Move the runtime compatibility gate procedure and the context field limits into reference files (e.g., references/runtime-compat.md, references/context-limits.md), keeping only the short version probe and gate check inline.

Reorder sections to follow the execution timeline — Prerequisites, Runtime gate, Preflight (auth/base/context), Choose depth and execution, Submit, Collect, Present, Act, Recover — so 'Submit and collect with --async' no longer precedes 'Preflight'.

DimensionReasoningScore

Conciseness

The depth-selection policy (--fast/--deep/auto) is restated in "Choose when and how deeply to review", again in "Checkpoints and final handoff", and a third time in "Configuration"; the "Runtime compatibility gate" and "Compatibility and limits" passages pack many caveats into single run-on sentences. This is noticeably verbose with several redundant sections, matching the 2 anchor rather than the 3 anchor's 'some unnecessary explanation' — though it never pads with concepts Claude already knows, so it stays above 1.

2 / 5

Actionability

Provides copy-paste-ready shell for async submission and the status-collection loop (with mktemp/trap cleanup and jq error handling), an exit-code decision table, exact provenance flags ("--skill qodo-review --skill-version 1.10.15 --distribution marketplace"), a concrete session-context JSON example, specific limits (64 KiB file, 50 decisions, 32,768-char bounds), and bounded recovery procedures. The instruction to "Confirm the exact flags with qodo review --help" is an explicit verification step, not a gap, so the 5 anchor fits better than 4.

5 / 5

Workflow Clarity

Validation is abundant and explicit: a version gate before any call, exit-code-driven collection handling, fix→verify→re-review feedback loops, and explicit stop conditions for unproductive loops. However, the top-level section order is non-linear — "Submit and collect with --async" precedes "Preflight", and lifecycle rules are scattered across "Checkpoints and final handoff", "Prepare a PR handoff", and "Configuration" — so the reader must reassemble the sequence, fitting the 4 anchor rather than the 5 anchor's clear end-to-end sequence.

4 / 5

Progressive Disclosure

All 8 referenced files exist in references/, are one level deep with no further nesting, and are clearly signaled with purpose and timing (e.g., "read [shell guidance](references/windows-shells.md) before the first call; [launcher recovery](references/windows-launcher.md) only if invocation fails"). The body still inlines dense material that belongs in references — the full runtime compatibility gate procedure, context field limits, and the complete collection script — so it matches the 4 anchor (good structure, minor organization gaps) rather than the 5 anchor's lean overview.

4 / 5

Total

15

/

20

Passed

Description

88%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: third-person voice, concrete multi-step capabilities, and explicit quoted trigger phrases with a clear when-to-use clause. It also draws an explicit boundary against the sibling qodo-review-resolver skill. The only gaps are a few missing natural trigger synonyms and slight generic overlap on the review-related triggers.

DimensionReasoningScore

Specificity

Quotes multiple concrete actions covering the full workflow: "Review local changes with Qodo", "Use light background checkpoints while coding", "collect and assess findings with session context", "run a final review before handing off", plus the resolver boundary "Use qodo-review-resolver for findings already posted on a PR". Coverage is comprehensive within the skill's scope, matching the 5 anchor rather than the 4 anchor's 'minor gaps'.

5 / 5

Completeness

Explicitly answers both questions: what ("Review local changes… Use light background checkpoints… collect and assess findings… run a final review") and when ("during substantive coding milestones and before a PR or completed-work handoff", reinforced by "Also use for 'review my local diff', 'pre-PR review', or 'run qodo review'"). The when-clause is explicit with concrete trigger phrases, matching the 5 anchor rather than the 4 anchor's 'could be more specific'.

5 / 5

Trigger Term Quality

Includes explicit user-voice trigger phrases ("review my local diff", "pre-PR review", "run qodo review") plus situational cues like "before a PR or completed-work handoff". A few natural variants (e.g., "code review", "review my changes") are missing, which fits the 4 anchor (good coverage, a few natural terms missing) better than the 5 anchor's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Qodo branding, a named tool, and the explicit boundary "Use qodo-review-resolver for findings already posted on a PR" establish a clear niche. However, the generic review triggers ("review my local diff", "pre-PR review") carry minor overlap risk with general code-review skills, fitting the 4 anchor (mostly distinct, minor overlap with closely related skills) rather than the 5 anchor's minimal conflict risk.

4 / 5

Total

18

/

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

antigravity-plugins/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.