finishing-a-development-branch

Verify feature branch tests pass before offering four finalization options.

Updated Apr 16, 2014
One-click install
npx skills add https://github.com/minhhh/dotfiles --skill finishing-a-development-branch-minhhh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/minhhh/dotfiles/tree/main/ai/.ai/gemini-superpowers/skills/finishing-a-development-branch
Command: npx skills add https://github.com/minhhh/dotfiles --skill finishing-a-development-branch-minhhh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that a feature branch is ready for integration by ensuring tests pass and guiding how to finalize work.

Core Features & Use Cases

  • Test verification: Run and confirm that all tests pass before finalizing.
  • Branch decision: Detect the base branch and offer four explicit finalization options.
  • Safe cleanup: Clean up worktrees and branches after a decision is executed, or preserve them if requested.

Quick Start

Initiate the finishing process by validating tests and presenting four clear options for how to proceed with 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 feature branch after tests pass?

Finalizing a git feature branch involves verifying all tests pass, detecting the base branch, and choosing to merge locally, push a pull request, keep the branch, or discard it with optional cleanup.

What are the options for finishing a development branch in git?

Finishing a development branch offers four deterministic options: merging locally, pushing a pull request, keeping the branch, or discarding it entirely.

Can I discard a git branch safely after failing verification?

Yes, you can discard a branch by selecting the discard option, which safely removes the worktree and branch, ensuring no unverified changes are merged into the base branch.

How does base-branch detection work when merging a feature branch?

Base-branch detection automatically identifies the parent branch before finalization, ensuring safety checks are applied correctly before any merge, pull request, or cleanup is executed.

Do I need to run tests before creating a pull request?

Yes, test verification is required before creating a pull request; the workflow ensures all tests pass before offering the option to push a PR or merge locally.

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

The best way to clean up worktrees after merging is selecting a finalization option that executes safe cleanup, automatically removing the worktree and branch unless you explicitly choose to preserve them.