finishing-a-development-branch

Verify tests and select merge, pull request, keep, or discard for a Git feature branch.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill removes uncertainty at the end of feature development by verifying tests, presenting deterministic integration choices, and guiding safe completion or disposal of a development branch.

Core Features & Use Cases

  • Test verification before integration: require passing tests and halt on failures to prevent regressions.
  • Four clear completion paths: merge locally with post-merge verification, push and create a pull request, keep the branch and worktree for later, or securely discard with explicit typed confirmation.
  • Worktree and branch cleanup: identify and remove associated worktrees and delete feature branches when appropriate to avoid clutter.
  • Use Case: After finishing a feature and confirming tests pass locally, select whether to merge into the base branch, open a PR for review, preserve the branch for future work, or discard the changes with confirmation.

Quick Start

Use the finishing-a-development-branch skill to verify tests and then choose to merge locally, create a pull request, keep the branch, or discard it.

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 safely merge a git feature branch after tests pass?

To merge a git feature branch safely, the skill verifies passing tests, merges locally into the base branch, re-runs tests post-merge, and cleans up the associated worktree to prevent dangling branches.

What is the best way to clean up a git worktree after finishing development?

Cleaning up a git worktree after development involves identifying the associated worktree, deleting the feature branch upon integration or discard, and removing the worktree directory to prevent repository clutter.

How do I discard a git feature branch without leaving dangling worktrees?

Discarding a git feature branch securely requires explicit typed confirmation to prevent accidental loss, followed by branch deletion and worktree cleanup to ensure no dangling references remain.

Can I open a pull request from a local feature branch after verifying tests?

Yes, you can open a pull request by pushing your verified feature branch to the remote repository, selecting the pull request integration path to initiate code review instead of merging locally.

What should I do if tests fail before merging a git feature branch?

If tests fail before merging a git feature branch, the integration process halts immediately to prevent regressions, requiring you to fix failures before selecting a merge, pull request, preserve, or discard action.

Does finishing a development branch work without a git worktree setup?

Finishing a development branch requires a Git-based repository and is optimized for worktree setups, explicitly identifying and cleaning associated worktrees during branch integration or disposal to avoid clutter.