skills/review-code/SKILL.md
--- name: review-code description: Performs code review via an isolated fresh agent to prevent confirmation bias. Use when the user asks to "review code", "review changes", or "code review", or when invoked by /resolve step 08. Do NOT use for reviewing PRs from GitHub (use review-pr skill instead). argument-hint: [--ticket <id>] [--base <branch>] [--fix] [--severity <level>] allowed-tools: Read, Glob, Grep, Bash, Edit, Write, AskUserQuestion, Agent --- # Code Review Skill Orchestrates code rev
npx skillsauth add nicolas-codemate/claudecodeconfig skills/review-codeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Orchestrates code review by delegating to an isolated code-reviewer agent.
The review MUST be performed by a fresh agent with NO prior conversation context. This prevents confirmation bias - an agent that participated in the implementation unconsciously validates its own approach instead of questioning it.
<constraints> - Do not review the code yourself in the current context — confirmation bias from "having seen" the implementation is exactly what we're guarding against. - Delegate to an Agent (`subagent_type: "code-reviewer"`). - The agent receives only: ticket content, plan content, git diff, and project CLAUDE.md. No conversation history, no implementation reasoning, no debugging context. - The agent prompt must be fully self-contained (all text inline, no file paths to read). - Display the agent's review report verbatim — do not filter or soften findings. </constraints>Required context (gathered by YOU, passed inline to the agent):
.claude-work/{ticket-id}/ticket.md -> TICKET_CONTENT.claude-work/{ticket-id}/plan.md -> PLAN_CONTENTPROJECT_RULESgit diff {base-branch}...HEAD
git diff {base-branch}...HEAD --stat
Agent:
subagent_type: code-reviewer
description: "Fresh code review {ticket-id}"
prompt: |
You are reviewing code for ticket {ticket-id}.
You have NO prior knowledge of this implementation. Review with fresh eyes.
<ticket>
{TICKET_CONTENT}
</ticket>
<implementation_plan>
{PLAN_CONTENT}
</implementation_plan>
<project_conventions>
{PROJECT_RULES}
</project_conventions>
<diff_stats>
{DIFF_STATS}
</diff_stats>
<diff>
{DIFF_CONTENT}
</diff>
Perform a complete code review following your review process.
Return the full review report in markdown format.
Display the review report returned by the agent verbatim.
Write review report to .claude-work/{ticket-id}/review.md
From .claude/ticket-config.json:
{
"review": {
"enabled": true,
"auto_fix": false,
"severity_threshold": "important",
"block_on_critical": true
}
}
pending: Review not yet startedin_progress: Review in progresscompleted: Review finished successfullyskipped: Review skipped (disabled or no implementation)failed: Review encountered an errorInvoked by /resolve workflow (step 08-review) or directly by the user.
development
Method to diagnose and raise the Lighthouse performance score of a public page (landing, marketing, home). Use when asked to improve Lighthouse/PageSpeed scores, when auditing the first uncached paint of a public page, or when a landing embedded in a SPA must reach a top score. Do NOT use for in-app screen performance (data loading, rendering). For a brand-new landing, the first recommendation is static HTML with no framework runtime — most of this skill exists for when that is not an option.
tools
Audits a project's Claude Code setup against real usage — mines the project's conversations (worktrees included), confronts the project's skills/agents/CLAUDE.md with best practices, and proposes adjustments or new skills/agents/rules. Use when the user asks to audit the project config, analyze project conversations, or find automation opportunities for the current project. Do NOT use for the global ~/.claude configuration (use /audit-config instead).
development
Coaching workflow orchestrator. Guides the developer through implementation without writing code.
development
Disciplined methodology for code architecture refactoring. Use when the user asks to refactor architecture, decouple code, restructure a family of classes, redesign an interface, or rename/reorganize a set of related components. Forces a big-picture analysis before any code is written. Do NOT use for simple bug fixes, feature additions, or single-file refactoring.