Menu
Use when verified implementation is ready and the user must choose whether to keep, merge, or publish the branch. Do NOT use before applicable checks pass.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when a request leaves material product, architecture, behavior, or scope decisions unresolved. Do NOT use for approved, well-bounded implementation work.
Use when 2 or more substantial tasks are independent, have disjoint state, and parallel execution will save meaningful time. Do NOT use for coupled or sequential work.
Use when implementing an approved written plan with dependent tasks in the current session. Do NOT use when the plan is missing, unapproved, or naturally parallel.
Use when receiving code review feedback that may be unclear or technically questionable and needs verification. Do NOT use for an unrequested general code review.
Use when a completed change is high-risk, crosses subsystem boundaries, or the user explicitly requests independent review. Do NOT use by default for low- or medium-risk changes.
Use when the user requests delegated implementation or multiple substantial tasks are genuinely independent without shared state. Do NOT use for coupled or ordinary single-task work.
| name | finishing-a-development-branch |
| version | 6.2.0 |
| category | workflow |
| description | Use when verified implementation is ready and the user must choose whether to keep, merge, or publish the branch. Do NOT use before applicable checks pass. |
Verify the actual change, then let the user choose integration.
Read ../using-superpowers/references/risk-policy.md.
Run the smallest complete check justified by risk:
If an applicable check fails, report it and stop. Do not claim completion.
Offer only applicable options:
Do not commit, merge, push, delete a branch, or remove a worktree without the authority required by user and project instructions.
Perform the chosen action. If merging locally, rerun the same risk-appropriate check on the merged result.
Only clean up a worktree created for this task and only after successful integration or an explicit discard request. Destructive discard requires exact confirmation of the branch and path.
