code-review
'Run a comprehensive code review on local source files. Use this skill when the user asks to review, audit, inspect, evaluate, or check code, even if they never use the word "review." Does not post comments to GitHub pull requests — use post-code-review-to-pr for that. Does not analyze architectural structure or module boundaries — use architectural-analysis for that. Does not explain code or a PR to build understanding before reviewing — use code-overview for that. Does not capture feedback on Han''s own skills — use han-feedback for that.'
npx skills add testdouble/han --skill code-review --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
When running a code review, follow the process outlined here. ## Project Context - git installed: !`which git 2>/dev/null || echo "not installed"` - CLAUDE.md: !`find . -maxdepth 1 -name "CLAUDE.md" -type f` - project-discovery.md: !`find . -maxdepth 3 -name "project-discovery.md" -type f` - personal config directory: !`echo "${CLAUDE_CONFIG_DIR:-$HOME/.claude}"` - project .han/config.md: !`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](../../references/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. ## Review Constraints Severity levels: - **Critical** — Must fix before merge. Security vulnerabilities, data corruption risk, breaking API changes, data isolation failures. - **Warning** — Should fix. Bugs that don't corrupt data, significant performance issues, missing required tests, missing error handli
- Project Context
- Review Constraints
- Task ID Assignment
- Step 1: Identify Changes
- Detect review context
- Step 1.5: Load Branch Context
- Step 2: Automated Quality Checks
- Step 3: Classify Change Size and Dispatch Review Agents
- Step 3.1: Classify the change
- Steps 3.2 to 3.5: Select, scope, and dispatch agents
- Step 4: Review All Changes
- Step 5: Documentation Compliance Analysis
- Documentation Sources
- Step 6: Documentation Freshness Review
What does the code-review skill do?
'Run a comprehensive code review on local source files. Use this skill when the user asks to review, audit, inspect, evaluate, or check code, even if they never use the word "review." Does not post comments to GitHub pull requests — use post-code-review-to-pr for that. Does not analyze architectural structure or module boundaries — use architectural-analysis for that. Does not explain code or a PR to build understanding before reviewing — use code-overview for that. Does not capture feedback on Han''s own skills — use han-feedback for that.'
How do I install it?
Run `npx skills add testdouble/han --skill code-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From testdouble/han, a repository with 154 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.