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
Planning with Files
SkillKeeps the plan on disk so a context reset cannot erase it.
Incremental Implementation
SkillLands features as thin vertical slices that each leave the build green.
scope-guard
SkillCatches an edit that lands outside the project you are in.
Comments(0)
Sign in to comment