What problem does it solve? When implementation work is done and tests pass, deciding how to integrate a development branch—merge locally, open a pull request, or keep it—often leads to inconsistent choices, lost worktrees, or accidentally deleted uncommitted files. This Skill enforces a safe, repeatable completion workflow. ## Core Features & Use Cases - Test-Gated Integration: Runs the full test suite first and stops if anything fails, so only green work gets integrated. - Environment-Aware Menus: Detects normal repos, named-branch worktrees, and detached HEAD states to present the correct merge/PR/keep options. - Safe Worktree Cleanup: Removes only self-created worktrees, refuses to force-delete uncommitted files without explicit confirmation, and prunes stale registrations. - Use Case: After finishing a feature in a git worktree, use this Skill to verify tests, merge into the confirmed base branch, re-test the merged result, and clean up the worktree without losing scratch files. ## Quick Start Use the finishing-a-development-branch skill to complete this branch now that all tests pass.