obra/superpowers@finishing-a-development-branch

Verify tests and present four integration options for finished git branches.

9|2|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/AllBeingsFuture/AllBeingsFuture --skill obra-superpowers-finishing-a-development-branch-allbeingsfuture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obra/superpowers@finishing-a-development-branch
Source: https://github.com/AllBeingsFuture/AllBeingsFuture/tree/main/electron/embedded-assets/skills/superpowers-finishing-branch
Command: npx skills add https://github.com/AllBeingsFuture/AllBeingsFuture --skill obra-superpowers-finishing-a-development-branch-allbeingsfuture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a safe, structured way to finish work on a development branch by verifying tests, presenting exact integration choices, and performing the selected git operations so teams avoid merging broken code or accidentally deleting work.

Core Features & Use Cases

  • Test Verification: Run the project's test suite and block integration until tests pass.
  • Structured Decision Flow: Present exactly four concise options: merge locally, push and create a PR, keep the branch, or discard the work.
  • Safe Execution & Cleanup: Execute the chosen workflow with safeguards including typed confirmation for destructive actions and optional git worktree cleanup.
  • Use Case: A developer who completed a feature and needs to either merge it into main, open a PR, preserve the worktree for later, or safely discard a stale branch.

Quick Start

Finish the current feature branch by verifying the test suite, determining the base branch, presenting the four options, and then execute your chosen option.

Frequently Asked Questions about obra/superpowers@finishing-a-development-branch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely finalize a git development branch and verify tests before merging?

To finalize a git development branch, you can run deterministic test verification, detect the base branch, and choose an exact integration option: merge locally, push for a pull request, keep the branch, or discard it.

What is the best way to manage git branch integration options after completing a feature?

The best way to manage git branch integration is by using a structured decision flow that presents exactly four options: local merge, push with pull request, preserve the worktree, or discard changes entirely.

How do I discard a stale git worktree without accidentally deleting unmerged work?

To discard a stale git worktree safely, use a workflow that requires typed confirmation for destructive operations before executing cleanup, ensuring unmerged work is not accidentally deleted.

Can I push a git feature branch and create a pull request only if tests pass?

Yes, you can block integration until tests pass by running deterministic test verification first, then selecting the push and create pull request option from the four-option prompt.

Does finishing a development branch require manual base-branch detection for a local merge?

No, finishing a development branch does not require manual base-branch detection; the workflow automatically determines the base branch before presenting the local merge or pull request options.