skills.rest
brixtonpham
brixtonphamCOMMUNITY
Explore all skills by this author →
GitHub

code-review

Automate code-review workflows with verification gates and subagent-driven reviews.

Updated Jan 28, 2026
Search Tags:#workflow#verification#subagent#quality-assurance#code-review#peer-review#technical-rigor
One-click install
npx skills add https://github.com/brixtonpham/claude-config --skill code-review-brixtonpham
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/brixtonpham/claude-config/tree/main/skills/code-review
Command: npx skills add https://github.com/brixtonpham/claude-config --skill code-review-brixtonpham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews are time-consuming and inconsistent without a disciplined protocol. This Skill ensures technical rigor, evidence-based reasoning, and a structured path from feedback to verified changes.

Core Features & Use Cases

  • Receiving feedback: evaluate input critically, restate requirements, and avoid performative agreement.
  • Requesting reviews: dispatch a subagent-driven code-review to gather diverse perspectives before proceeding.
  • Verification gates: require fresh verification evidence (tests, builds, or checks) before claiming completion or merging.
  • Guardrails: maintain a strict sequence (READ -> UNDERSTAND -> VERIFY -> EVALUATE -> RESPOND -> IMPLEMENT) to ensure changes are technically sound.

Quick Start

Initiate a code-review session on the latest feature branch and follow the standard verification gates before claiming completion.

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 in an automated workflow?▼

Evidence-based code reviews are enforced by applying a strict READ -> UNDERSTAND -> VERIFY -> EVALUATE -> RESPOND -> IMPLEMENT sequence, requiring fresh verification evidence like tests or builds before merging.

How do I automate peer reviews using subagents before a merge?▼

Automated peer reviews are handled by dispatching a subagent-driven code-review process to gather diverse technical perspectives, centralize verification, and provide structured escalation paths when failures occur.

How do I stop performative agreement during technical feedback sessions?▼

Performative agreement is eliminated by critically evaluating input, restating requirements, and following a protocol-driven response process to ensure changes are technically sound.

What are verification gates in a code review workflow?▼

Verification gates in a code review workflow are mandatory checkpoints requiring fresh verification evidence, such as passing tests, successful builds, or automated checks, before claiming completion or merging code.

How do I structure an escalation path for code review failures?▼

Escalation paths for code review failures are structured through a centralized verification protocol that enforces technical rigor and ensures failures are addressed systematically before proceeding.

Can I use this code review protocol for subagent-driven development?▼

Yes, this code review protocol is explicitly designed for subagent-driven development, applying verification gates and evidence-based reasoning across receiving feedback, requesting reviews, and pre-merge checks.

Related Skills

Explore More Software Engineering Skills→
scruffydanscruffydan

verification-before-completion

Run verification commands and report results with evidence before completion.

Community
Basic
jikig-aijikig-ai
12

postmerge

Automate post-merge verification of CI, production health, and file freshness.

Official
Advanced
andregusman-raizandregusman-raiz
19

ag-publicar-deploy

Deploy code to preview, production, or rollback environments with automated smoke tests.

Community
Advanced
roanbrasilroanbrasil
5

static-analysis

Automate static analysis for Java, Kotlin, Python, and Rust codebases.

Community
Advanced