From superpowers
Use when implementation is complete to verify and finalize work directly on main/master
How this skill is triggered — by the user, by Claude, or both
Slash command
/superpowers:finishing-a-development-branchThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Guide completion of development work in a no-branch flow.
Guide completion of development work in a no-branch flow.
Core principle: Verify tests → summarize changes → ask for commit decision.
Announce at start: "I'm using the finishing-a-development-branch skill to complete this work."
Before finalizing, verify tests pass:
# Run project's test suite
npm test / cargo test / pytest / go test ./...
If tests fail:
Tests failing (<N> failures). Must fix before completing:
[Show failures]
Cannot finalize this work until tests pass.
Stop. Don't proceed to Step 2.
If tests pass: Continue to Step 2.
# Must be main or master
git branch --show-current
If not on main or master, stop and ask the user how to proceed.
Present exactly these 2 options:
Implementation complete on <current-branch>. What would you like to do?
1. Commit changes now on <current-branch>
2. Keep changes uncommitted for now
Which option?
Don't add explanation - keep options concise.
git add <relevant-files>
git commit -m "<message>"
Report: "Keeping changes uncommitted on ."
| Option | Commit | Leave Uncommitted |
|---|---|---|
| 1. Commit now | ✓ | - |
| 2. Keep as-is | - | ✓ |
Skipping test verification
Open-ended questions
Never:
Always:
main or masterCalled by:
Pairs with:
npx claudepluginhub martinzokov/superpowers-mz --plugin superpowersGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.