finishing-branch

Verifies finished feature branches by testing and offering merge options.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finalizing a development branch can be error-prone without a defined process. This guide automates the decision flow by validating tests and presenting structured options for completing the work.

Core Features & Use Cases

  • Automates test verification before finalizing a branch.
  • Enforces a four-option decision flow: merge locally, push and create a PR, keep the branch, or discard.
  • Handles base-branch detection and cleanup of worktrees when applicable.

Quick Start

Run this skill after finishing a feature branch to verify tests and choose among merge locally, push PR, keep as-is, or discard.

Frequently Asked Questions about finishing-branch

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

FAQPage Schema
How do I verify tests before merging a git feature branch?

Verify tests before merging a git feature branch by running a workflow that validates tests and detects the base branch. It then guides you to merge locally, create a PR, keep, or discard safely.

What is the best way to clean up local git branches after finishing a feature?

The best way to clean up local git branches after finishing a feature is to use a decision flow that detects the base branch and handles worktree cleanup automatically. It offers discard or merge options after test validation.

How do I decide whether to merge locally or create a pull request for my branch?

To decide whether to merge locally or create a pull request, this workflow applies a four-option decision flow based on your base branch and test results. It provides explicit choices for predictable outcomes.

Do I need to manually detect the base branch before finalizing a pull request?

You do not need to manually detect the base branch before finalizing a pull request. The workflow automatically handles base-branch detection and enforces test verification before presenting structured completion options.

When should I discard a feature branch instead of keeping it for later?

You should discard a feature branch instead of keeping it when test verification fails or the work is no longer needed. The workflow presents discarding as one of four explicit options after validating tests and detecting the base branch.