What problem does it solve? When implementation work is done, developers face a risky moment: deciding how to integrate a feature branch without losing work, merging into the wrong base, or destroying uncommitted files in a worktree. This Skill enforces a safe, structured completion workflow. ## Core Features & Use Cases - Test-Gated Integration: Runs the full test suite first and refuses to proceed if anything fails, including re-verifying tests on the merged result. - Environment-Aware Options: Detects normal repos, named-branch worktrees, and detached HEAD states to present the correct menu: merge locally, push and create a PR, or keep the branch as-is. - Safe Worktree Cleanup: Removes only self-created worktrees under .worktrees/ or worktrees/, never force-removes worktrees containing uncommitted files, and requires typed confirmation before discarding work. - Use Case: After finishing a feature in a git worktree, use this Skill to verify tests, merge back to the base branch, clean up the worktree, and delete the feature branch without losing any uncommitted notes or plans. ## Quick Start Use the finishing-a-development-branch skill to complete my current branch now that all tests pass.