What are Verification Gates?

Verification Gates are mandatory checkpoints that require fresh, documented evidence (like test outputs or build logs) before any claim of success or completion can be made.

What coding principles does this skill enforce?

The skill strictly enforces YAGNI (You Ain't Gonna Need It), KISS (Keep It Simple, Stupid), and DRY (Don't Repeat Yourself) to ensure code remains lean and maintainable.

How does this skill handle code review feedback?

It uses a specific 'READ → UNDERSTAND → VERIFY' protocol that prioritizes technical evaluation over polite agreement, requiring technical verification before any changes are implemented.

Does this skill work with subagents?

Yes, it is specifically designed for subagent-driven development, providing a framework to dispatch a code-reviewer subagent via the Task tool after each completed task.

Can I use this before creating a Pull Request?

Absolutely. It is recommended to use the Requesting Review protocol and Verification Gates before committing code or opening a PR to ensure all requirements are met and tested.

Code Reviewer & Verification Rigor

Name: Code Reviewer & Verification Rigor
Author: CongDon1207

byCongDon1207

•

Collaboration Tools

Enforces technical rigor and evidence-based verification throughout the development lifecycle to ensure code quality and prevent false completion claims.

About

This skill transforms the development workflow by implementing three core practices: technical feedback reception, systematic subagent-driven reviews, and strict verification gates. It prioritizes technical correctness over social comfort, requiring raw evidence—such as test logs and build results—before any task is marked as complete. By strictly adhering to YAGNI, KISS, and DRY principles, it ensures that implementations are lean, verified, and free from performative agreement, making it an essential tool for high-stakes subagent-driven development and complex pull requests.

Key Features

Strict verification gates requiring evidence before any completion/success claims.
Technical feedback protocol that prioritizes rigor over performative agreement.
1 GitHub stars
Enforcement of YAGNI, KISS, and DRY principles during the review process.
Integrated decision trees for handling feedback and status reporting.
Systematic review dispatching via specialized code-reviewer subagents.

Use Cases

Verifying task completion and testing outcomes in subagent-driven development.
Conducting 'brutal' technical reviews before merging major features into main branches.
Managing and prioritizing unclear or conflicting feedback from external reviewers.

About

Key Features

Strict verification gates requiring evidence before any completion/success claims.
Technical feedback protocol that prioritizes rigor over performative agreement.
1 GitHub stars
Enforcement of YAGNI, KISS, and DRY principles during the review process.
Integrated decision trees for handling feedback and status reporting.
Systematic review dispatching via specialized code-reviewer subagents.

Use Cases

Verifying task completion and testing outcomes in subagent-driven development.
Conducting 'brutal' technical reviews before merging major features into main branches.
Managing and prioritizing unclear or conflicting feedback from external reviewers.