finishing-a-development-branch

Validate tests, detect the base branch, and present four integration options.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/BryceRoberts13/superpowers-for-antigravity --skill finishing-a-development-branch-bryceroberts13
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/BryceRoberts13/superpowers-for-antigravity/tree/main/skills/finishing-a-development-branch
Command: npx skills add https://github.com/BryceRoberts13/superpowers-for-antigravity --skill finishing-a-development-branch-bryceroberts13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams finalize feature work by ensuring tests pass and presenting a clear path for integration or cleanup.

Core Features & Use Cases

  • Test verification: runs or confirms the project's test suite has passed.
  • Base-branch determination: finds the appropriate base branch (main/master) for merge operations.
  • Structured decision options: presents four explicit actions: merge locally, push and create PR, keep the branch as-is, or discard the work.
  • Post-action cleanup: cleans up worktrees and branches after completion.

Quick Start

Run the finishing-a-development-branch skill after tests pass to decide how to merge or clean up.

Frequently Asked Questions about finishing-a-development-branch

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

FAQPage Schema
How do I finalize a git feature branch after tests pass?

Finalizing a git feature branch involves validating tests, detecting the base branch, choosing an integration path like merge or pull request, and cleaning up the branch afterwards.

What is the best way to clean up git worktrees after merging a branch?

Cleaning up git worktrees after merging is handled by post-action cleanup, which removes obsolete worktrees and branches automatically once the integration decision is completed.

How do I decide between a local merge and a pull request for my branch?

Choosing between a local merge and a pull request is structured by presenting four explicit options: merge locally, push and create a PR, keep the branch, or discard the work entirely.

Can I automatically detect the base branch for a git merge?

Yes, base-branch determination automatically finds the appropriate base branch, such as main or master, ensuring your git merge operations target the correct integration branch.

Does this branch finalization workflow require external dependencies?

No, this branch finalization workflow requires no external dependencies, operating entirely within your existing git environment to validate tests and manage cleanup decisions.