What problem does it solve? When implementation work is done, developers face an ambiguous decision point: merge locally, open a pull request, keep the branch, or discard it. This Skill removes that ambiguity by verifying tests, detecting the git environment, and presenting a fixed set of structured options with safe execution and cleanup. ## Core Features & Use Cases - Test-Gated Completion: Refuses to present merge or PR options until the project's test suite passes, preventing broken code from being integrated. - Environment-Aware Menus: Detects normal repositories, named-branch worktrees, and detached HEAD states, then presents the correct 4-option or 3-option menu. - Safe Worktree Cleanup: Uses provenance checks to only remove worktrees under .worktrees/ or worktrees/, always from the main repo root, followed by git worktree prune. - Control Tower Integration: Detects CT-governed dispatches via .agent/SLICE.md and follows a fixed push-PR-release-stop path, leaving merges as human decisions. - Use Case: After finishing a feature branch in a git worktree, invoke this Skill to verify tests, choose "Push and create a Pull Request", and keep the worktree alive for PR iteration. ## Quick Start Use the finishing-a-development-branch skill to complete my current branch now that all tests pass.
