finishing-a-development-branch

Verify tests, determine base branch, and execute one of four integration workflows.

1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/xiaobin/superpowers-kimi --skill finishing-a-development-branch-xiaobin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/xiaobin/superpowers-kimi/tree/main/.agents/skills/finishing-a-development-branch
Command: npx skills add https://github.com/xiaobin/superpowers-kimi --skill finishing-a-development-branch-xiaobin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finishing a development branch can be uncertain without a clear path for integration. This skill guides completion by presenting a structured options for merging, opening a pull request, keeping the branch, or discarding changes after tests pass.

Core Features & Use Cases

  • Verifies tests pass before offering options to ensure safe integration.
  • Determines the appropriate base branch to anchor the final workflow.
  • Presents exactly four actions (merge locally, push and PR, keep as-is, or discard) and executes the chosen path with cleanup.

Quick Start

After your implementation passes all tests, run this skill to select one of four integration options and carry out the chosen workflow.

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 after implementation is complete?

Finishing a git development branch requires verifying tests pass first. This skill then determines the correct base branch and guides you through choosing to merge locally, open a pull request, keep the branch, or discard changes.

What are my options for merging a git feature branch cleanly?

For merging a git feature branch cleanly, you can choose from four options: merge locally, push and open a pull request, keep the branch as-is, or discard the changes, followed by automatic resource cleanup.

Does finishing a git branch require tests to pass before merging?

Yes, this workflow verifies that tests pass before offering any integration options. This ensures safe integration by confirming implementation stability before allowing you to merge, open a pull request, keep, or discard your branch.

How do I clean up local git branches after merging a pull request?

Cleaning up local git branches after merging is handled automatically. The skill executes your chosen workflow and performs resource cleanup, removing the finished development branch once the integration path is complete.

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

You should discard a git development branch when tests pass but the changes are no longer needed. The skill includes discarding as one of its four finishing options, executing the deletion alongside automatic resource cleanup.