finishing-a-development-branch

Verify tests and present deterministic merge, PR, or cleanup options for Git feature branches.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/bbohhu-prog/waxs --skill finishing-a-development-branch-bbohhu-prog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/bbohhu-prog/waxs/tree/main/.claude/skills/superpowers/finishing-a-development-branch
Command: npx skills add https://github.com/bbohhu-prog/waxs --skill finishing-a-development-branch-bbohhu-prog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the finalization of a development branch by validating tests and presenting deterministic merge/PR/cleanup options to avoid missteps.

Core Features & Use Cases

  • Verify tests pass before merging and presenting four explicit options.
  • Determine base branch automatically and propose next steps.
  • Offer deterministic workflows: merge locally, push and create PR, keep branch as-is, or discard.
  • Optional cleanup of worktrees after a chosen action to maintain a clean repository.
  • Applicable to typical Git-based feature-branch workflows across teams.

Quick Start

Run the finishing-a-development-branch skill after all tests pass to choose a final merge or cleanup action.

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 development branch and choose between merging or creating a pull request?

Finalizing a development branch involves verifying tests pass and then selecting from deterministic options like local merge, push for PR, keep as-is, or discard. The skill presents these four explicit choices after detecting the base branch.

What's the best way to clean up git worktrees after merging a feature branch?

Cleaning up git worktrees after merging is handled through optional cleanup steps triggered after choosing a final action. This maintains a clean repository state once the development branch integration is complete.

Do I need to run tests before merging a git feature branch?

Running tests before merging a git feature branch is required. The skill implements guarded steps that verify tests pass before presenting any merge, pull request, or cleanup options to prevent integration missteps.

Can I determine the base branch automatically when finishing a development workflow?

Determining the base branch automatically is supported when finishing a development workflow. The skill detects the appropriate base branch and uses it to propose the next deterministic integration steps.

What are my options if I want to keep a git branch as-is instead of merging?

Keeping a git branch as-is is one of the four explicit deterministic workflows offered. Alongside local merge, push for PR, or discard, this option allows you to pause integration while maintaining the current branch state.

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

A guided workflow for git branch cleanup prevents missteps by enforcing test verification and offering deterministic merge options. Manual commands risk errors, whereas this approach validates state and provides explicit post-merge actions.