What problem does it solve? When implementation work is done and tests pass, developers face an error-prone decision point: how to integrate the branch, whether to open a pull request, and how to clean up git worktrees without losing uncommitted files. This Skill provides a disciplined, step-by-step procedure that prevents premature merges, accidental data loss, and forgotten cleanup. ## Core Features & Use Cases - Test-Gated Integration: Runs the full test suite first and blocks any merge or PR until the suite is green, including re-verifying tests on the merged result. - Environment-Aware Menus: Detects normal repos, named-branch worktrees, and detached HEAD states via git-dir comparison, then presents the correct integration options (merge locally, push and create PR, or keep as-is). - Safe Worktree Cleanup: Removes only self-created worktrees under .worktrees/ or worktrees/, refuses forced deletion when uncommitted files exist, and requires explicit typed confirmation before discarding work. - Use Case: After finishing a feature in an isolated git worktree, use this Skill to verify tests, confirm the base branch, present integration options to the user, and clean up the worktree only after a successful local merge. ## Quick Start Use the finishing-a-development-branch skill to verify my tests and help me integrate this completed feature branch.
