code-review

Enforce verification gates and evidence-based claims during code reviews.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Code review is often hindered by performative agreement and vague feedback. This Skill enforces technical rigor, structured evaluation, and verification before any completion claims, helping teams ship higher-quality code.

Core Features & Use Cases

  • Receiving Feedback: follow a disciplined response pattern that restates requirements, verifies against the codebase, and tests items one-by-one.
  • Requesting Reviews: dispatch the code-reviewer subagent to validate implementation against plan and requirements.
  • Verification Gates: require fresh verification evidence before claiming success, builds, or merged status.

Quick Start

Follow the Response Pattern: READ → UNDERSTAND → VERIFY → EVALUATE → RESPOND → IMPLEMENT; if feedback is unclear, stop and request clarification. Then, decide whether to dispatch a code-reviewer for formal review before proceeding.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I enforce evidence-based code reviews before merging a pull request?

To enforce evidence-based code reviews, apply verification gates that require fresh verification evidence before any completion, build, or merge claims are accepted. This ensures feedback and changes are technically sound rather than relying on performative agreement.

What is the best way to manage vague feedback during a subagent-driven code review?

Managing vague feedback requires following a disciplined response pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, then IMPLEMENT. If feedback remains unclear during code review, you must stop and request clarification before proceeding.

How do I dispatch a code-reviewer subagent to validate implementation against requirements?

To dispatch a code-reviewer subagent, initiate a formal review request after completing a development task. The subagent validates your implementation against the original plan and requirements to ensure technical rigor before merging.

Does this code review process require any specific dependencies or environments?

This code review process requires a subagent-driven development environment and the code-reviewer subagent component. It operates without external dependencies, using internal reference handling to manage receiving feedback and confirming completion.

When should I not use automated verification gates for pull requests?

Automated verification gates for pull requests are not suitable when you cannot provide fresh verification evidence. The process strictly prohibits claiming success, builds, or merged status without running new verification checks against the codebase.