superpowers-finishing-a-development-branch

Guide merge, PR, or cleanup decisions for a finished development branch.

2|1|Updated Oct 21, 2025
One-click install
npx skills add https://github.com/aldoborrero/agent-kit --skill superpowers-finishing-a-development-branch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superpowers-finishing-a-development-branch
Source: https://github.com/aldoborrero/agent-kit/tree/main/skills/superpowers/finishing-a-development-branch
Command: npx skills add https://github.com/aldoborrero/agent-kit --skill superpowers-finishing-a-development-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finishing a development branch can be risky without a structured, repeatable process. This skill provides a safe, guided way to verify tests, determine the base branch, and choose a clear post-workflow option to merge, open a PR, or clean up the branch.

Core Features & Use Cases

  • Verifies test results on the feature branch before proceeding with any integration step.
  • Determines the appropriate base branch (e.g., main or master) and clarifies the correct merge destination.
  • Presents four explicit options to handle completion: local merge, PR creation, keeping the branch, or discarding the work.
  • Performs optional cleanup of the worktree and feature branch according to the chosen path.
  • Use Case: A developer completes changes on a feature branch with green tests and needs a safe hand-off to the team while preserving or removing the feature branch as appropriate.

Quick Start

Begin by ensuring your branch tests pass, then instruct the agent to guide the finalization by presenting the four options.

Frequently Asked Questions about superpowers-finishing-a-development-branch

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

FAQPage Schema
How do I safely finish a development branch and decide between merging or opening a pull request?

To finish a development branch safely, run tests first, then use a guided workflow that verifies tests, determines the base branch, and presents explicit options for local merge, pull request creation, branch retention, or discarding work.

What is the best way to clean up a feature branch after passing tests?

The best way to clean up a feature branch is to follow a structured finalization process that verifies green tests, identifies the correct base branch, and performs optional worktree and branch cleanup based on your chosen merge or pull request path.

Can I automate git branch management and merge strategy selection for my team?

Yes, you can automate git branch management by applying a guided workflow that enforces safety checks, verifies tests, determines the base branch, and presents four clear merge, pull request, or cleanup options for structured cutover.

Does this branch finalization workflow support both main and master base branches?

Yes, the branch finalization workflow supports common base branches by automatically determining the appropriate merge destination, whether your repository uses main, master, or another base branch for integration.

What happens if my feature branch tests are not passing before a merge?

If feature branch tests are not passing, the finalization workflow enforces a verification step that prevents proceeding with any integration step, ensuring only branches with green tests reach the merge or pull request stage.

Why should I use a guided process for development branch cleanup instead of manual git commands?

A guided process for development branch cleanup reduces risk by enforcing structured, repeatable steps with explicit prompts and safety checks, preventing accidental data loss during merge, pull request creation, or branch deletion.