Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →testdouble/code-review
Run a comprehensive code review on local source files.
Passed 7 of 13 test cases with the skill, and 5 of 13 without it.
and 6 more in the full report
8 fixed4 passed either way5 still failing5 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
A code change alters a public API signature, making the documentation file `docs/api-reference.md` inaccurate. What category prefix should be assigned to this documentation issue?
| Checked | Without skill | With skill |
|---|---|---|
| Uses [Docs Update: docs/api-reference.md] or [Docs Update: api-reference.md] as the category prefix | Missed | Passed |
The instructions your model reads when the skill loads.
When running a code review, follow the process outlined here.
which git 2>/dev/null || echo "not installed"find . -maxdepth 1 -name "CLAUDE.md" -type ffind . -maxdepth 3 -name "project-discovery.md" -type fbash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh" 2>/dev/null || echo "$HOME/.claude"cat .han/config.md 2>/dev/null || echo ""As your first action, use the Read tool on .han/config.md inside the personal config directory path above. A read
that returns no file is no personal configuration: continue silently. When that file or the project .han/config.md
probe supplies content, apply it per config-rule.md, which governs precedence
between the two files, relative-path resolution, and what to do with a file that reads but cannot be used.
Severity levels:
Severity calibration is governed by Step 3.3 (the authoritative home for size-based demotion). Manual findings from
Steps 4 to 6 follow the same size-based rules as agent findings classified at Step 7: Small changes escalate only
Critical findings and default uncertain ones to the lower severity, Medium changes escalate Critical and Warning, Large
changes prefer the higher severity when in doubt. Read {size} from Step 3.1. Include file_path:line_number
references and code examples for suggested fixes.
Finding caps: Manual review findings (Steps 4-6) and agent findings (Step 7) are each capped at 30 items. Prioritize by severity: all CRIT first, then WARN, then SUGG. If either cap is exceeded, note that additional items were omitted and another code review is recommended after addressing current items. Security findings are not capped (see classification rubric).
Project pattern deference: A pattern that differs from general best practices but is consistent within the project is not a review finding. Only flag deviations from the project's own conventions.
test cases passed, vs 5 / 13 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.