finishing-a-development-branch

Verify tests and guide merge, PR, or cleanup decisions for git branches.

5|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/mrtolkien/GHOST --skill finishing-a-development-branch-mrtolkien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/mrtolkien/GHOST/tree/main/vendor/superpowers/finishing-a-development-branch
Command: npx skills add https://github.com/mrtolkien/GHOST --skill finishing-a-development-branch-mrtolkien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides teams to finish development by verifying completion criteria and presenting deterministic options for merging, PR creation, or cleanup.

Core Features & Use Cases

  • Stepwise verification of tests to ensure stability before finalizing work.
  • Deterministic decision points: merge locally, push and open PR, keep as-is, or discard work.
  • Supports cleanup of worktrees and integration with existing git workflows for coordinated releases.

Quick Start

Start by validating tests, then choose one of the four completion options to finalize the branch.

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 branch after development work is complete?

Finalizing a git branch involves verifying tests pass, determining the base branch, choosing to merge locally or open a pull request, and optionally cleaning up worktrees to keep the repository organized.

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

The best way to clean up git worktrees after merging is to select a completion option that executes the branch merge and then performs optional worktree cleanup, removing stale working directories and maintaining a tidy environment.

How do I verify tests before merging a git branch into the main codebase?

To verify tests before merging a git branch, run a stepwise validation process against your CI or local test suite to ensure branch stability, presenting deterministic merge or pull request options only after tests pass.

Can I choose between opening a pull request or merging locally when finishing a git branch?

Yes, you can choose between merging locally, pushing to open a pull request, keeping the branch as-is, or discarding work, providing deterministic decision points for collaborative software projects using git workflows.

Does this branch finalization workflow support collaborative projects with CI test suites?

Yes, this workflow applies to collaborative software projects using git workflows with CI or test suites, ensuring branches mature toward completion by validating tests before presenting merge or cleanup decisions.

When should I discard work instead of merging a development branch?

You should discard work instead of merging when stepwise test verification fails or the feature is no longer needed, selecting the discard option from the deterministic completion choices to remove the unwanted branch.