finishing-a-development-branchlisted

# Finishing a Development Branch ## Overview **Core principle:** Verify tests → Verify both gates, audit and review → Detect environment → Present options → Execute choice → Clean up. **Announce at start:** "I'm using the finishing-a-development-branch skill to complete this work." ## Step 1: Verify Tests Run the project's full test suite (`npm test` / `cargo test` / `pytest` / `go test ./...`). **Report the run in the evidence line, whichever way it went** — this is the last thing your human partner reads before a merge option is on the table, and a bare count ("6/6 green") does not say which instrument produced it: **Command:** [verbatim] — **exit:** [code] — **counts:** [passed/failed/skipped]. From the run you made on the tree you are about to integrate, never one carried from earlier in the session. **If tests fail**, report the failures and stop — the menu comes after a green suite: ``` Tests failing (<N> failures). Must fix before completing: [Show failures] ``` **If tests pass:** continue to Step 2. ## Step 2: Verify the Two Gates **Two gates stand between a green suite and the menu, and this step checks both.** They ran in this order — superpowersplus:final-branch-audit first, then the whole-branch review — and this step does not re-run them: it establishes that each one ran and what it returned. Checking one and assuming the other is how a branch reaches the menu with a gate nobody opened. ### 2a. The conformance audit A green suite proves the code tha