skills.rest
XCmiaow
XCmiaowCOMMUNITY
Explore all skills by this author →
GitHub

finishing-a-development-branch

Verify tests and present four Git branch integration options.

Updated May 5, 2026
Search Tags:#git#pull request#branch management#test verification#merge workflow#release readiness#worktree cleanup
One-click install
npx skills add https://github.com/XCmiaow/cc-deploy --skill finishing-a-development-branch-xcmiaow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/XCmiaow/cc-deploy/tree/main/skills/finishing-a-development-branch
Command: npx skills add https://github.com/XCmiaow/cc-deploy --skill finishing-a-development-branch-xcmiaow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you finish a development branch safely by ensuring tests pass and then guiding you through merge, PR creation, preserving the branch for later, or discarding it with confirmation—so you avoid broken merges and accidental deletions.

Core Features & Use Cases

  • Test-gated completion: Requires running the project’s test suite before offering any integration actions, stopping immediately if failures exist.
  • Deterministic integration choices: Presents exactly four actionable options (local merge, push+PR, keep as-is, or discard) to remove ambiguity at the end of development.
  • Safety-guarded cleanup: Cleans up git worktrees for the appropriate options (merge locally and discard) and requires typed confirmation for discarding.

Quick Start

Use this skill after you’ve finished coding changes and want to confirm tests pass, determine the correct base branch, and select merge, PR, keep, or discard in one structured flow.

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 branch safely before merging?▼

To finish a git branch safely, run the project test suite and verify all tests pass before choosing to merge locally, open a pull request, keep the branch, or discard it with confirmation.

What is the best way to manage a git branch after passing tests?▼

The best way to manage a git branch after tests pass is selecting one of four deterministic integration choices: local merge, push and pull request, keep as-is, or discard with mandatory typed confirmation.

How does test verification work for a git merge workflow?▼

Test verification in a merge workflow requires running the project test suite first, stopping the integration process immediately if any test failures exist to prevent broken merges.

Can I discard a git branch with unmerged work safely?▼

You can discard a git branch safely by selecting the discard option, which requires typed confirmation and cleans up associated git worktrees to prevent accidental deletions.

Do I need to detect a base branch before opening a pull request?▼

Yes, you need to detect a suitable base branch to properly complete a feature-branch workflow and ensure the pull request or local merge targets the correct integration point.

Related Skills

Explore More Software Engineering Skills→
tom-xstom-xs

using-git-worktrees

Create and manage isolated git worktrees with submodule awareness.

Community
Advanced
the-agency-aithe-agency-ai
39

Post-Merge

Verify merged pull requests, merge origin updates, and create GitHub releases.

Official
Advanced
aberrantCodeaberrantCode
1

finishing-a-development-branch

Verify tests pass and merge, open a PR, retain, or delete a Git branch.

Community
Intermediate
dsifrydsifry
7

pr-shepherd

Monitor GitHub pull requests and resolve CI failures until merge.

Community
Advanced