finishing-a-development-branch

Validate tests and execute merge, pull request, keep, or discard actions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides the completion of development work through rigorous test verification, structured options for merging or pushing, and systematic cleanup. It ensures clean merges, prevents incomplete or broken code from being integrated, and streamlines the final steps of your development workflow, saving time and reducing errors.

Core Features & Use Cases

  • Mandatory Test Verification: Ensures all project tests pass as a critical first step before any completion claims or merges.
  • Structured Options: Presents clear, predefined choices for completing work: merge locally, push and create a Pull Request, keep the branch, or discard the work.
  • Automated Cleanup: Handles branch deletion and worktree cleanup for selected options, maintaining a tidy repository.
  • Use Case: You've finished a feature on a development branch. Use this skill to verify tests, choose to merge it to main, and automatically handle all the necessary Git operations and cleanup, ensuring a smooth and error-free integration.

Quick Start

Use the finishing-a-development-branch skill to complete the work on 'feature-branch-X' and merge it into the main 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 complete a development branch with test verification and cleanup?

Completing a development branch involves running tests to verify code quality, selecting a merge or push option, and automating cleanup. This Skill validates tests pass, presents options to merge locally, create a Pull Request, keep the branch, or discard work, then executes your choice with required Git cleanup.

What happens if tests fail when finishing a development branch?

Tests must pass before any merge or Pull Request can proceed. If tests fail, the Skill halts completion and prevents integration of broken code, ensuring only verified work reaches your base branch.

Can I merge a development branch locally to main without creating a Pull Request?

Yes. After test verification, this Skill offers four concrete options: merge locally to your base branch, push and create a Pull Request, keep the branch as-is, or discard the work entirely. You choose the path that fits your workflow.

Does this Skill handle branch and worktree cleanup automatically?

Cleanup is automated for merge and discard paths only. After merging locally or discarding work, the Skill removes the development branch and cleans up worktrees, maintaining a tidy repository without manual Git commands.

How do I safely discard a development branch without losing work accidentally?

Discard requires explicit confirmation to prevent accidental loss. The Skill enforces strict rules demanding user acknowledgment before removing your branch and worktree, ensuring you intend to abandon the work.

What's the best way to structure the final steps of a Git workflow after feature work?

Structured completion combines mandatory test validation, predefined merge or push options, and systematic cleanup. This approach prevents incomplete code integration, reduces manual error, and streamlines your development workflow from feature completion through repository maintenance.