code-review

Delegate code reviews to a fresh agent and return the report verbatim.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/nicolas-codemate/claudeCodeConfig --skill code-review-nicolas-codemate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/nicolas-codemate/claudeCodeConfig/tree/main/skills/code-review
Command: npx skills add https://github.com/nicolas-codemate/claudeCodeConfig --skill code-review-nicolas-codemate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unbiased code reviews by using a fresh agent with no prior context, preventing confirmation bias.

Core Features & Use Cases

  • Isolated code-reviewer subagent ensures no cross-talk from prior implementations.
  • Works for /resolve step 08, /review-code, and user prompts like "review code" or "code changes".
  • Returns the agent's review report verbatim and stores it to .claude/feature/{ticket-id}/review.md.

Quick Start

Delegate a fresh code review to the code-reviewer using the provided inputs.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get an unbiased code review for my git diff without confirmation bias?

To get an unbiased code review, this Skill delegates your git diff to a fresh AI agent with no prior context. It prevents confirmation bias by feeding the agent only ticket content, the plan, and project CLAUDE.md.

How do I automate code reviews within my software engineering workflow?

Automated code reviews trigger through the /resolve workflow step 08, the /review-code command, or direct prompts. The agent processes the inputs and returns the review report verbatim for immediate use.

What inputs do I need to prepare for an AI agent code review?

AI agent code reviews require ticket content, a development plan, the git diff, and the project CLAUDE.md file. Providing these inputs ensures the agent has the necessary context to generate an accurate review.

Does an isolated code-reviewer agent prevent cross-talk from prior implementations?

An isolated code-reviewer agent prevents cross-talk by using a fresh subagent for every review. It evaluates the git diff independently, ensuring prior implementation context does not influence the review report.

Where is the code review report stored after the agent finishes processing?

The code review report is stored locally at .claude/feature/{ticket-id}/review.md. The agent returns the review report verbatim and saves it to this path for future reference.

When should I use a fresh agent for code reviews instead of my current AI assistant?

Use a fresh agent for code reviews when you need to prevent confirmation bias from prior context. It works best for unbiased software engineering checks where prior implementation knowledge could skew results.