finishing-a-development-branch

Verify tests, present disposition options, and clean up worktrees for feature branches.

3|2|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/woxiangyangzhimao/skills --skill finishing-a-development-branch-woxiangyangzhimao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/woxiangyangzhimao/skills/tree/main/finishing-a-development-branch
Command: npx skills add https://github.com/woxiangyangzhimao/skills --skill finishing-a-development-branch-woxiangyangzhimao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of completing a development branch, ensuring code quality and maintaining branch integrity.

Core Features & Use Cases

  • Automated Branch Verification: Ensures all tests pass before presenting disposition options.
  • Branch Disposition Options: Allows for merging, creating a Pull Request, keeping, or discarding the branch.
  • Worktree Cleanup: Cleans up worktrees based on user choice.
  • Use Case: After a feature branch is fully developed and tested, this Skill helps decide the next steps, whether it's merging into the main branch, creating a Pull Request, or archiving the branch.

Quick Start

Execute the finishing-a-development-branch skill to finalize your 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 finalize a development branch and clean up the worktree after tests pass?

To finalize a development branch, you can automate test verification and then choose to merge, create a Pull Request, keep, or discard it. The selected disposition automatically triggers the corresponding worktree cleanup.

What is the best way to manage feature branch completion and code integration?

Managing feature branch completion involves running automated tests, selecting a disposition option like merging or creating a Pull Request, and cleaning up worktrees. This ensures code quality and maintains branch integrity throughout the integration process.

Do I need GitHub CLI to create a Pull Request when finishing a git workflow branch?

You need git for branch operations and possibly the GitHub CLI (gh) to create a Pull Request. The skill uses these dependencies to automate branch verification and present disposition options for your feature branch.

Can I discard a feature branch instead of merging it into the main branch?

Yes, you can discard a feature branch instead of merging. The skill presents multiple disposition options including merging, creating a Pull Request, keeping, or discarding the branch, followed by automated worktree cleanup.

Why does branch verification require tests to pass before presenting disposition options?

Branch verification requires tests to pass to ensure code quality and maintain branch integrity before integration. Automating this test verification prevents broken code from being merged, creating a Pull Request, or kept in the worktree.

Does this branch management process work with standard git workflows?

Yes, this branch management process works with standard git workflows by automating test verification, presenting disposition options, and cleaning up worktrees. It requires git for branch operations and optionally gh for Pull Request creation.