finishing-a-development-branch

Verify tests and guide Git branch merge, PR, keep, or discard decisions.

14|1|Updated Dec 29, 2011
One-click install
npx skills add https://github.com/doitian/dotfiles-public --skill finishing-a-development-branch-doitian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/doitian/dotfiles-public/tree/main/ai/workflows/superpowers/skills/finishing-a-development-branch
Command: npx skills add https://github.com/doitian/dotfiles-public --skill finishing-a-development-branch-doitian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After implementing a feature and passing tests, this skill guides how to integrate the work by offering a structured decision path for merge, PR, or cleanup.

Core Features & Use Cases

  • Verify tests pass and determine readiness to merge or evolve the branch.
  • Present exactly four options: merge locally, push and create PR, keep as-is, or discard.
  • Cleanup worktrees and branches according to the selected option, with safe guardrails.

Quick Start

After tests pass, present four concise options for merging, creating a PR, keeping, or discarding the feature branch.

Frequently Asked Questions about finishing-a-development-branch

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

FAQPage Schema
What is the best way to finish a Git development branch after tests pass?

To finish a development branch, verify tests pass, select a base branch, then execute one of four integration options: merge locally, push and create a PR, keep the branch, or discard it with optional cleanup.

How do I choose between merging locally or opening a pull request for my feature branch?

Choosing between merging locally or opening a pull request depends on your team workflow; this skill presents both options alongside keeping or discarding the branch, allowing you to select the appropriate Git integration path after tests pass.

How do I clean up Git worktrees and branches after merging a feature?

To clean up Git worktrees and branches after merging, select the merge or discard option in the workflow, which triggers safe guardrails to remove the worktree and delete the branch seamlessly.

When should I discard a development branch instead of keeping it?

You should discard a development branch instead of keeping it when the feature is no longer needed or tests fail, utilizing the discard option to safely remove the branch and clean up the associated worktree.

Does this Git branch management workflow support selecting different base branches for integration?

Yes, this Git branch management workflow supports selecting different base branches, allowing you to specify the target branch before executing the merge, pull request, or discard actions.