finishing-a-development-branch

What problem does it solve? When implementation work is done and tests pass, developers still face a risky decision: how to integrate the 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 stops if anything fails, so only green work gets integrated. - Environment-Aware Options: Detects normal repos, named-branch worktrees, and detached HEAD states, then presents the correct merge/push/keep menu. - Safe Worktree Cleanup: Removes only self-created worktrees, refuses to force-delete uncommitted files without explicit confirmation, and verifies the merged result before deleting branches. - Use Case: After finishing a feature in a Git worktree, use this Skill to verify tests, merge back to the base branch, confirm the merged result is green, and clean up the worktree without losing scratch files. ## Quick Start Use the finishing-a-development-branch skill to complete this work now that implementation is done and tests pass.