finishing-a-development-branch

What problem does it solve? When implementation work is done, developers often 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 structured set of options with safe execution and cleanup. ## Core Features & Use Cases - Test Gate Before Completion: Runs the project's test suite first and refuses to proceed with merge or PR creation if any tests fail. - Environment-Aware Options: Detects normal repos, 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 it created, changes to the main repo root before removal, and runs git worktree prune for self-healing. - Use Case: After finishing a feature in a git worktree, invoke this Skill to verify tests pass, choose "Push and create a Pull Request", and have the branch pushed with a structured PR body while the worktree is preserved for review iteration. ## Quick Start Ask the assistant to finish the current development branch and walk you through merge, pull request, keep, or discard options.