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 first, then presenting exactly four structured options and executing the chosen workflow safely. ## Core Features & Use Cases - Test Gate Before Completion: Runs the project's test suite (npm test, cargo test, pytest, go test) and blocks any merge or PR if tests fail. - Four Structured Options: Presents merge locally, push and create PR, keep branch as-is, or discard work, then executes the chosen path with the correct git commands. - Safe Cleanup and Discard Protection: Cleans up git worktrees only when appropriate and requires typed 'discard' confirmation before permanently deleting branches and commits. - Use Case: After finishing a feature branch in a git worktree, invoke this Skill to verify tests pass, create a pull request via gh pr create, and clean up the worktree in one guided flow. ## Quick Start Ask the assistant to finish the current development branch and choose whether to merge it, open a pull request, keep it, or discard it.