Finishing a Development Branch
Closes finished branch work through a fixed order: green suite, then a choice, then cleanup.
Install
/plugin install superpowers@claude-plugins-official
Runs when implementation is done and the tests pass, before the branch is merged, pushed or abandoned.
- Author
- Jesse Vincent (obra)
- License
- MIT
The full test suite runs first and a red suite ends the process there — no integration menu is offered over failing tests. The environment is then read from git itself, because a normal checkout, a named-branch worktree and a detached HEAD each need different handling. Only after that does the agent ask how to integrate: merge locally, open a pull request, or leave the branch alone. The base branch is confirmed out loud before any merge, since merging into the wrong one is expensive to undo.
Similar skills
Git Advanced Workflows
SkillCovers the Git commands people avoid until something goes wrong.
TDD Workflows
SkillSplits red, green and refactor into separate commands so no production code gets written during red.
Using Git Worktrees
SkillPrepares an isolated workspace for feature work, falling back to a git worktree.
Comments(0)
Sign in to comment