finishing-a-development-branch

Finalize a development branch by closing epics, verifying tests, and presenting integration options.

Updated Dec 15, 2025
One-click install
npx skills add https://github.com/OpenSourceSam/v2_heras_garden --skill finishing-a-development-branch-opensourcesam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/OpenSourceSam/v2_heras_garden/tree/main/.claude/skills/finishing-a-development-branch
Command: npx skills add https://github.com/OpenSourceSam/v2_heras_garden --skill finishing-a-development-branch-opensourcesam

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of completing a development branch, ensuring code quality and proper integration back into the main codebase.

Core Features & Use Cases

  • Epic Closure: Automatically closes associated development epics and tasks.
  • Test Verification: Mandates passing tests before integration.
  • Integration Options: Presents clear choices for merging, creating pull requests, or discarding work.
  • Worktree Management: Handles cleanup of development worktrees.
  • Use Case: After successfully implementing a new feature and passing all tests, use this Skill to safely merge your changes into the main branch or create a pull request for review.

Quick Start

Use the finishing-a-development-branch skill to finalize the current development 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 git development branch and merge it back to the main codebase?

Finalizing a development branch requires verifying passing tests and closing associated epics before presenting integration options like merging or creating a pull request, culminating in worktree cleanup.

Can I create a pull request directly from my current development branch?

Yes, creating a pull request is a presented integration option using the gh dependency, available alongside merging or discarding work after mandatory test verification is completed.

Do I need to pass all tests before merging a development branch?

Yes, passing tests is a mandatory verification step before you can proceed with merging or creating a pull request, enforced by the strict 6-step process to ensure proper code integration.

What is the best way to clean up git worktrees after integrating a branch?

The best way is to let the branch finalization process handle worktree cleanup automatically based on your chosen integration path, whether you merge, create a pull request, or discard the work.

How do I discard development work and close associated epics in git?

To discard development work, you must use the branch finalization process which requires explicit confirmation before discarding, ensuring intentional closure of associated epics and proper worktree cleanup.

Does this branch finalization process work with GitHub for code integration?

Yes, the branch finalization process works with GitHub for code integration through the gh dependency, allowing you to create pull requests directly and manage branch integration back into the main codebase.