gustavo-meilus/superpipelines / plugins/superpipelines/skills/finishing-a-development-branch
finishing-a-development-branch
VerifiedStructured integration protocol that enforces a test-verification gate and presents branch disposition options (merge, PR, keep, or discard). Use when implementation is complete, all tests pass, and an integration decision for the development branch is pending.
Finishing a Development Branch — Integration Protocol
Ensures work is integrated or preserved according to explicit user choice. A mandatory test verification gate is enforced before any options are presented, preventing promotion of broken or unverified code to the base branch.
The Completion Protocol
2. DETERMINE BASE BRANCH
- The split point is identified (e.g.,
git merge-base HEAD main). - The base branch is confirmed with the user if ambiguity exists.
3. PRESENT STRUCTURED OPTIONS
- Exactly these four options are presented without modification:
- Merge back to [base] locally
- Push and create a Pull Request
- Keep the branch as-is (Handle later)
- Discard this work
4. EXECUTE CHOICE
- Option 1: Base is checked out, latest is pulled, branch is merged, tests are re-verified, and the feature branch is deleted.
- Option 2: Branch is pushed to origin and a PR is created using the
ghCLI. - Option 4: Explicit typed confirmation ("discard") is required before destructive deletion.
5. CLEANUP
- For Options 1, 2, and 4: The associated git worktree is removed to maintain repository hygiene.
Completion Patterns
Red Flags — STOP
- "I'll merge now and fix the tests later." → STOP. Integration of failing code is a SEV-0 failure.
- "What should I do next?" → STOP. Present the four structured options defined in the protocol.
- "Deleting worktree automatically." → STOP. Option 3 requires worktree preservation.
Rationalization Table
<rationalization_table>
| Excuse | Reality |
|---|---|
| "PR handles testing anyway." | Local verification prevents broken builds and reduces CI overhead. |
| "It's just a one-line change." | One-line changes are the leading cause of "it worked in my head" regressions. |
| "Discarding is faster than cleanup." | Unconfirmed discards cause irreversible data loss. |
| </rationalization_table> |
Reference Files
sk-worktree-safety/SKILL.md— Worktree management.verification-before-completion/SKILL.md— Final evidence gate.running-a-pipeline/SKILL.md— Integration point for pipeline completion.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |