finishing-a-development-branch

Automate Git branch completion with merge, PR, and cleanup options.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Completing development work in Git often involves a series of steps (testing, merging, cleanup) that can be missed or done incorrectly, leading to broken main branches or orphaned worktrees.

Core Features & Use Cases

  • Automated Test Verification: Ensures all tests pass before offering completion options, preventing broken merges.
  • Structured Completion Options: Presents clear choices for merging, creating a Pull Request, keeping the branch, or discarding work.
  • Automated Cleanup: Handles branch deletion and worktree removal based on the chosen option, maintaining a clean environment.
  • Use Case: After finishing a feature, use this skill to verify all tests pass and then choose to merge your changes, create a Pull Request, or clean up your development environment.

Quick Start

I've completed the 'feature/user-profile' branch. Use the finishing-a-development-branch skill to finalize my work.

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 safely merge a Git branch after code review and testing?

Branch completion involves verifying tests pass, choosing a merge strategy, and cleaning up. This Skill automates that workflow by presenting your options—merge locally, create a pull request, preserve the branch, or discard it—then executes your choice and removes orphaned worktrees, preventing broken merges to main.

What's the best way to finish a development branch without breaking the main branch?

Automated test verification and structured decision flow prevent errors. This Skill checks that all tests pass before offering completion options, ensuring only validated code reaches main, and handles branch deletion and cleanup based on your chosen merge path.

Can I automate cleanup after merging a Git branch?

Yes. Cleanup automation removes deleted branches and orphaned worktrees based on your completion option. This Skill handles it as part of the merge workflow, maintaining a clean development environment after you finish a feature branch.

How do I decide between merging locally or creating a pull request?

The choice depends on your workflow and code review process. This Skill presents both options after tests pass, lets you select the approach that fits your team's approval requirements, then executes the merge or PR creation automatically.

What happens if tests fail when I try to complete a branch?

Test verification is built into the completion workflow. If tests fail, the Skill blocks merge options and reports the failure, preventing broken code from reaching main until all tests pass.

Does this work with Git workflows that use multiple base branches?

Yes. The Skill determines the base branch as part of its structured decision flow, supporting typical workflows where features merge to develop or main depending on your branching strategy.