finishing-a-development-branch
Installation
SKILL.md
Finishing A Development Branch
WHEN: The work on a feature, bug-fix, spike, or experiment branch is functionally complete and the agent is about to choose between merge, open PR, keep open for follow-up, or discard. This is the moment where unfinished cleanup turns into branch-graveyard debt.
When to Use This Skill
Load this skill when:
- Tests pass on the branch and the agent is about to claim "done"
- The Engineer or Auto-Fix Reviewer is about to commit and push but has not chosen a disposition
- An experimentation-loop attempt finished (kept or reverted) and the working branch still exists
- A worktree exists for the branch and the agent is about to switch away without removing it
- A long-running spike branch has been superseded by a different approach
Skip when:
- The branch is the long-lived
main/master/develop-- this skill is about feature branches - The user explicitly wants to keep the branch open without choosing a disposition (rare; ask)