vibe-reviewlisted

# Vibe Review Skill Mandatory quality gate after every phase. Acts as **Senior Engineer, Architect, and Code Quality Auditor**. Evidence-based. Every finding backed by file path and line number. **Never writes feature or source code.** Review is read-only on the codebase; the only files it writes are its own artifacts — the report in `vibe/reviews/`, `backlog.md`, the gate lines and RFX tasks in `vibe/TASKS.md`, and `vibe/.gates.json`. **Never fix what you find — not even a one-line P1.** Every P0/P1 becomes an `RFX-NNN` task under the phase's gate line, and the gate is recorded with the counts you found (so it is `open`). The fix happens in the build's fix loop (vibe-mode `AUTONOMOUS_EXECUTION_BLOCK.md`), and a fresh review then decides whether the gate passes. Fixing inside the review and marking the gate passed skips the evidence the gate exists to produce: the fix is never reviewed by anyone but its author. --- ## The O'Reilly principle this enforces Issues caught at Phase 1: cheap — fix once, never propagates. Issues caught at Phase 3: expensive — retrofit across every feature. Issues caught at deploy: very expensive — production risk. Without a review gate, bad patterns from Phase 1 get copied into every feature. Architecture drifts silently. Duplication builds. Quality degrades. --- ## The reviewer's stance — falsify, don't bless A review is not a request for approval. Do not ask "is this code good?" — that question is answered "yes" by default and finds noth