finishing-a-development-branch

Guides completion of development branches through merge, pull request, or cleanup options.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/NT-boop-star/BRMV-tract --skill finishing-a-development-branch-nt-boop-star
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/NT-boop-star/BRMV-tract/tree/main/antigravity/skills/finishing-a-development-branch
Command: npx skills add https://github.com/NT-boop-star/BRMV-tract --skill finishing-a-development-branch-nt-boop-star

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When implementation work is done, developers often face ambiguity about how to integrate the branch, risking broken merges, forgotten worktrees, or accidentally deleted work. This Skill enforces a safe, structured completion workflow. ## Core Features & Use Cases - Test Gate Before Integration: Verifies the project's test suite passes before offering any merge or PR options, stopping the process if failures exist. - Four Structured Completion Options: Presents exactly four choices—merge locally, push and create a PR, keep the branch as-is, or discard the work—and executes the chosen path. - Safe Discard and Worktree Cleanup: Requires typed confirmation before deleting work and cleans up git worktrees only for the appropriate options. - Use Case: After finishing a feature branch with all tests green, invoke this Skill to decide between merging into main locally or opening a GitHub pull request with a generated summary and test plan. ## Quick Start Ask the assistant to finish the current development branch and present the integration options after verifying tests pass.

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 finish a git feature branch after implementation?

Verify the test suite passes first, then choose between merging locally into the base branch, pushing and creating a pull request, keeping the branch, or discarding it. This Skill walks through each option and handles branch deletion and worktree cleanup.

How to create a GitHub pull request from the command line?

Push the feature branch with git push -u origin, then run gh pr create with a title and body containing a summary and test plan. The Skill generates this PR automatically when you choose the pull request option.

What happens if tests fail before merging a branch?

The process stops immediately and reports the number of failing tests. No merge or pull request options are presented until the failures are fixed and the test suite passes.

Does this workflow clean up git worktrees automatically?

Worktrees are removed only after a local merge or a confirmed discard. When creating a pull request or keeping the branch as-is, the worktree is preserved so the work remains accessible.

Can I recover a branch after choosing the discard option?

No. Discard permanently deletes the branch and its commits using git branch -D, which is why the Skill requires typing 'discard' as explicit confirmation before proceeding.