finishing-a-development-branch

Close the bd epic, verify tests, and present four integration options.

80|17|Updated Oct 27, 2025
One-click install
npx skills add https://github.com/withzombies/hyperpowers --skill finishing-a-development-branch-withzombies
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/withzombies/hyperpowers/tree/main/skills/finishing-a-development-branch
Command: npx skills add https://github.com/withzombies/hyperpowers --skill finishing-a-development-branch-withzombies

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the final steps of a development workflow, ensuring that completed work is properly integrated, tests are verified, and branches are cleaned up. It streamlines the process of closing bd epics, creating Pull Requests, or discarding work, preventing manual errors and inconsistencies.

Core Features & Use Cases

  • Epic Closure & Test Verification: Automatically closes the bd epic and verifies all tests pass before offering integration options.
  • Structured Integration Options: Presents clear choices for merging locally, creating a Pull Request, keeping the branch, or discarding work.
  • Automated Cleanup: Handles branch deletion and worktree removal based on the chosen integration option.
  • Use Case: After a feature's implementation has been reviewed and approved, use this Skill to close the bd epic, verify all tests, and then choose to either merge the branch, create a PR, or discard the work.

Quick Start

Use the finishing-a-development-branch skill to complete the current 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 after completing a feature?

Finalizing a development branch closes your epic, verifies tests pass, then presents four integration options: merge locally, create a Pull Request, keep the branch for later, or discard the work. The Skill automates this entire workflow, including branch cleanup based on your choice.

What happens to my branch after I choose an integration option?

After you select an option—merge, PR, keep, or discard—the Skill automatically handles cleanup. If you merge or discard, the branch and worktree are removed. If you keep it, the branch remains available for future work.

Can I use this workflow if my tests haven't passed yet?

No. Test verification is enforced before the Skill presents integration options. All tests must pass before you can proceed with branch finalization, ensuring only validated code moves forward.

What's the difference between merging locally and creating a Pull Request?

Merging locally integrates your branch directly into the main branch on your machine. Creating a Pull Request submits your work for remote review and integration through your repository's PR workflow, enabling team review and CI checks.

Do I need to manually close the bd epic before using this Skill?

No. The Skill automatically closes the bd epic as part of finalization. You only need to trigger it once your implementation is complete and tests pass.

What if I want to discard my work after starting finalization?

The discard option removes your branch and worktree after confirmation. This is useful when experimentation is complete or a feature is no longer needed, providing a clean slate for your next task.