finishing-a-development-branch

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

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Syedyasir001/RVULibPass --skill finishing-a-development-branch-syedyasir001
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/Syedyasir001/RVULibPass/tree/main/.agent/skills/library/finishing-a-development-branch
Command: npx skills add https://github.com/Syedyasir001/RVULibPass --skill finishing-a-development-branch-syedyasir001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When implementation work is done, developers often face ambiguity about how to integrate the branch safely. This Skill removes that guesswork by verifying tests first, then presenting exactly four structured options for merging, creating a pull request, keeping, or discarding the work. ## Core Features & Use Cases - Test Gate Before Integration: Runs the project's test suite (npm test, cargo test, pytest, go test) and blocks any merge or PR if tests fail. - Structured Completion Options: Presents exactly four choices—merge locally, push and create a PR via gh CLI, keep the branch as-is, or discard with typed confirmation. - Worktree Cleanup: Detects and removes git worktrees for merged or discarded branches while preserving them when the branch is kept. - Use Case: After finishing a feature branch in a git worktree, invoke this Skill to verify tests pass, create a pull request with a summary and test plan, and clean up the worktree automatically. ## Quick Start Use the finishing-a-development-branch skill to complete my current feature branch and help me decide whether to merge it or open a pull request.

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

First verify the project's test suite passes, then choose one of four options: merge locally into the base branch, push and create a pull request, keep the branch as-is, or discard it. The Skill walks through each path including worktree cleanup.

How to create a pull request from a feature branch using gh CLI?▼

Push the branch with git push -u origin, then run gh pr create with a title and a body containing a summary of changes and a test plan checklist. The Skill generates this PR body structure automatically.

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 is offered 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, the worktree is preserved so the work remains accessible.

How do I safely delete a feature branch without losing work accidentally?▼

The discard option requires typing the exact word 'discard' after showing the branch name, commit list, and worktree path that will be deleted. Only then does it force-delete the branch with git branch -D.