ship

Use the /ship loop, which runs code-reviewer, security-reviewer, and qa-reviewer in parallel and relies on a review-gate hook that blocks any commit lacking an APPROVE verdict for the exact diff. The gate reads each reviewer's VERDICT line and stores it against the diff hash.

The loop launches a tdd-guide agent that writes a failing test before any implementation, and every fix round must also start with a failing test rather than a direct patch. For QA findings, the fix is the missing test itself.

Fix rounds are capped at 3. Only the reviewers that flagged issues re-run on the new diff, and if CRITICAL or HIGH findings remain after the third round, the loop stops and escalates the pending findings to the human without committing.

No. The loop ends at an open pull request created with gh pr create on a ship/ branch. Merging and deploying are explicitly reserved for the human operator.

The gate only covers commits made through the Bash tool by the agent; a manual git commit bypasses it. Work larger than 3-5 files must be split into separately mergeable phases by the planner first.

The qa-reviewer drives the external awesome-qa-skills system, requiring at minimum the discover-testing router and the testing-types skills installed flat under ~/.claude/skills. Without them it falls back to the project's common testing rules.