code-review

Verify code changes with formal reviews and evidence before merging.

3|Updated Jan 17, 2026

Search Tags:#verification #governance #code-quality #subagent #code-review #pull-request #review-process

Ready to run

npx skills add https://github.com/zircote/agents --skill code-review-zircote

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/zircote/agents/tree/main/skills/code-review
Command: npx skills add https://github.com/zircote/agents --skill code-review-zircote

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures disciplined, evidence-based code reviews to prevent biases, misinterpretation, and premature completion claims during development.

Core Features & Use Cases

Receiving feedback with technical rigor and structured pushback
Requesting formal reviews via code-reviewer subagent
Enforcing verification gates with evidenced results before completion
Essential for subagent-driven development, pull requests, and major refactors

Quick Start

Submit the changes you want reviewed to trigger the code-review workflow and ensure verification before merging.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I enforce code review verification gates before merging a pull request?▼

You can enforce code review verification gates by triggering a formal review workflow that requires documented evidence of technical correctness before allowing a merge. This ensures disciplined, evidence-based verification for pull requests.

What is subagent-driven development and how does it handle code reviews?▼

Subagent-driven development uses a code-reviewer subagent to request formal reviews and enforce verification gates. This prevents biases and premature completion claims by requiring documented evidence before merging code changes.

How do I ensure technical correctness during major feature work or refactoring?▼

To ensure technical correctness during major refactors, apply rigorous review practices that identify and verify code changes through structured pushback and formal verification. This prevents misinterpretation and enforces governance before completion.

Can I use structured pushback to receive feedback with technical rigor?▼

Yes, you can receive feedback with technical rigor by applying structured pushback during the review process. This enforces evidence-based verification and prevents premature completion claims during subagent-driven development.

When do I need formal verification and documented evidence for code changes?▼

You need formal verification and documented evidence for code changes during major feature work, pull requests, and subagent-driven development. This enforces technical rigor and prevents biases before merging.