What is the 'Iron Law of Review' in this skill?

The Iron Law dictates that the AI must only report issues where it has a confidence score of 80% or higher, ensuring that reviews are actionable and free from stylistic noise or vague suspicions.

How does this skill handle existing code issues?

The skill is designed to focus on the current implementation. Pre-existing issues are assigned a confidence score of 0 and are discarded to keep the review scope focused on the new changes.

Why does the skill return a BLOCKED status?

A BLOCKED status occurs when no verifiable test output is found in the project's learning logs. This prevents 'fake' approvals and ensures that the code has actually been executed and passed tests.

Is E2E testing required for all changes?

E2E evidence is required specifically for user-facing changes, such as UI updates, API changes, and user workflows. Internal refactors may only require unit test evidence.

Dev Workflow Code Reviewer

Name: Dev Workflow Code Reviewer
Author: edwinhu

byedwinhu

협업 도구

Enforces rigorous, confidence-based code reviews with mandatory test evidence gates to ensure high-integrity software delivery.

소개

The Dev Review skill acts as a high-integrity quality gate for software development, specifically designed as the final verification phase of the /dev workflow. It transforms Claude into a disciplined reviewer that refuses to approve changes without verifiable test evidence—including mandatory E2E test results for user-facing features. By applying the 'Iron Law of Review,' the skill filters out subjective nitpicks and low-confidence noise, focusing exclusively on issues with an 80% or higher confidence score. This ensures that every approval is based on objective evidence rather than assumptions, significantly reducing bugs and regression risks.

주요 기능

Confidence-Based Filtering: Only reports issues with a 80% or higher confidence score to eliminate review noise.
Spec Compliance Mapping: Cross-references implementation against SPEC.md to ensure all requirements are met.
Honesty-First Protocol: Prevents 'fraudulent' approvals by requiring verified output rather than assumed passes.
Mandatory Test Output Gate: Blocks review process if actual test results are missing from the project learnings.
E2E Evidence Requirement: Specifically mandates end-to-end verification for all UI and user-facing changes.
0 GitHub stars

사용 사례

Enforcing a 'test-first' culture by preventing code merges without verifiable E2E or Unit test evidence.
Reducing developer fatigue by focusing reviews on high-priority functional issues rather than stylistic preferences.
Standardizing code quality and testing requirements across automated development workflows.

소개

주요 기능

Confidence-Based Filtering: Only reports issues with a 80% or higher confidence score to eliminate review noise.
Spec Compliance Mapping: Cross-references implementation against SPEC.md to ensure all requirements are met.
Honesty-First Protocol: Prevents 'fraudulent' approvals by requiring verified output rather than assumed passes.
Mandatory Test Output Gate: Blocks review process if actual test results are missing from the project learnings.
E2E Evidence Requirement: Specifically mandates end-to-end verification for all UI and user-facing changes.
0 GitHub stars

사용 사례

Enforcing a 'test-first' culture by preventing code merges without verifiable E2E or Unit test evidence.
Reducing developer fatigue by focusing reviews on high-priority functional issues rather than stylistic preferences.
Standardizing code quality and testing requirements across automated development workflows.