Runs the Implement→Review→Test→Fix cycle until the work is actually clean, with evidence. Use after any non-trivial implementation and before claiming it is done.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
The quality loop prevents premature "done" declarations. Keep iterating until the review is clean and the tests pass, and show the evidence.
vibe-doc-quality-gate)Implement → Self-review diff → Run checks ─┬─ clean + green → EXIT
↑ │
└──────── Fix issues ←──────┘
Review the diff — Read the whole diff as a reviewer would. If the harness has a built-in review command (for example /code-review in Claude Code or /review in Codex), run it. Otherwise check for:
vibe-scope-guard)vibe-anti-rationalization-check)Run the project's own checks — Use what the repo defines (Makefile, package.json scripts, CI workflow) rather than guessing:
go test -race)Fix only the issues found. Don't add features while fixing.
Loop back to step 1. Track the iteration count.
Exit when the review is clean and all checks pass. Quote the final check output. Don't paraphrase it.
Iterations: X · Final status: CLEAN / KNOWN_ISSUES
| Iteration | Issues found | Fixed |
|---|---|---|
| 1 | [list] | [list] |
Final checks: [command] → [result]
Remaining known issues (if any):
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Validates completed work against defined acceptance criteria. Use after completing a task that has specific success criteria defined in issues, specs, or task descriptions.
The English summary is being prepared. Showing the original description.
Generates edge case, failure mode, and spec-driven test cases. Covers boundary values, nil inputs, concurrency, resource exhaustion, malformed data, and requirement-linked traceability tests. Use after happy-path tests exist and before claiming coverage is complete, when requirements lack tests, or before a security review.
The English summary is being prepared. Showing the original description.
Catches shortcuts and reward hacking — weakening or deleting tests to make them pass, hard-coding expected outputs, silently dropping requirements, or claiming work is done without running it. Use before declaring a task complete and whenever a test or requirement feels like it's in the way.
The English summary is being prepared. Showing the original description.
Safely integrates commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees.
The English summary is being prepared. Showing the original description.
Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering. Use when writing tests that involve goroutines, async operations, or shared mutable state.
The English summary is being prepared. Showing the original description.
Enforces tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test traceability, and spec-to-code implementation mapping. Use before claiming code is complete.
The English summary is being prepared. Showing the original description.