finishing-a-development-branch

Present four merge/PR options after tests pass for a development branch.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finishes a development branch after tests pass by presenting structured merge/PR options for clean integration.

Core Features & Use Cases

  • Verify tests pass and determine the base branch.
  • Present exactly four options: Merge locally, Push and create PR, Keep the branch as-is, or Discard.
  • Automatically perform optional cleanup and provide guardrails to avoid destructive actions.

Quick Start

Trigger the finishing workflow to verify tests, choose a merge option, and clean up 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
How do I finish a git development branch after tests pass?

Finishing a git development branch involves verifying tests pass, detecting the base branch, and choosing a structured integration path such as merging locally or pushing to create a pull request.

What are my options for merging a feature branch into the base branch?

When merging a feature branch, your options are to merge locally, push and create a pull request, keep the branch as-is, or discard the changes entirely, with optional cleanup applied afterward.

Can I automatically discard changes and clean up a git branch after deciding not to merge?

Yes, you can discard changes and clean up a git branch by selecting the discard option, which applies guardrails to prevent destructive actions while safely removing the feature branch.

Does the git branch integration workflow require passing tests before creating a pull request?

Yes, the git branch integration workflow requires all tests to pass before offering structured merge or pull request options, ensuring only verified feature branches proceed to integration.

What is the best way to handle base branch detection when finalizing a feature branch?

The best way to handle base branch detection is to use a deterministic workflow that automatically identifies the base branch, ensuring your merge or pull request targets the correct integration point.