finishing-a-development-branchlisted

# Finishing a Development Branch ## Overview Guide completion of development work by presenting clear options and handling 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." ## The Process <!-- nicopowers-finishing-return-loop:start --> ### Step 0: Confirm the Return Loop Require proof that Simplify ran before final review: the proof names the diff examined and the light scan outcome. If proof is absent, return to the active implementation workflow and run the scan before continuing. Then evaluate whether the completed work produced a qualifying repository lesson. **REQUIRED SUB-SKILL:** Use `nicopowers:compounding`. It writes nothing when no lesson qualifies and at most one lesson when one does. <!-- nicopowers-finishing-return-loop:end --> ### Step 1: Verify Tests **Before presenting options, verify tests pass:** ```bash # Run project's test suite npm test / cargo test / pytest / go test ./... ``` **If tests fail:** ``` Tests failing (<N> failures). Must fix before completing: [Show failures] Cannot proceed with merge/PR until tests pass. ``` Stop. Don't proceed to Step 2. **If tests pass:** Continue to Step 2. ### Step 2: Detect Environment **Determine workspace state before presenting options:** ```bash GIT_DIR=$(cd "$(git rev-parse --git-dir)" 2>/dev/null && pwd -P) GIT_COMMON=$(cd "$(git r