finishing-a-development-branchlisted

<!-- Adapted from superpowers (https://github.com/obra/superpowers), MIT (c) Jesse Vincent. --> # Finishing a Development Branch ## Overview Guide completion of development work by presenting clear options and handling the chosen workflow. **Core principle:** Verify tests → detect environment → present options → execute choice → clean up. **Announce at start:** "I'm using the finishing-a-development-branch skill to complete this work." ## Fits in the pipeline The exit ramp of **Stage 6 (Build)** for each feature branch, just before the **Stage 7 per-feature QA gate** and **Stage 8 ship**. It enforces the principle #8 rule — no merge/PR without green tests — and keeps worktrees (from `using-git-worktrees`) clean. Priority: **user > skills > default**; `_shared/vibegod-principles.md` apply. Do not treat a clean merge here as "shipped"; the QA gates still run. ## The Process ### Step 1: Verify Tests Run the project's suite (`npm test` / `cargo test` / `pytest` / `go test ./...`). If tests fail: report the failures, state "Cannot proceed with merge/PR until tests pass," and STOP — don't reach Step 2. If they pass, continue. (Use `verification-before-completion` — fresh evidence.) ### Step 2: Detect Environment ```bash GIT_DIR=$(cd "$(git rev-parse --git-dir)" 2>/dev/null && pwd -P) GIT_COMMON=$(cd "$(git rev-parse --git-common-dir)" 2>/dev/null && pwd -P) ``` | State | Menu | Cleanup | |-------|------|---------| | `GIT_DIR == GIT_COMMON` (normal repo) | Standard 4 optio