finishing-a-development-branch

Verify tests and execute merge, PR, keep, or discard actions for Git branches.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/tim-hub/role-based-skills --skill finishing-a-development-branch-tim-hub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/tim-hub/role-based-skills/tree/main/finishing-a-development-branch
Command: npx skills add https://github.com/tim-hub/role-based-skills --skill finishing-a-development-branch-tim-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers conclude feature work by verifying test status, presenting a strict set of integration choices, and performing the chosen git operations while protecting against accidental data loss.

Core Features & Use Cases

  • Test Verification: Ensures the project's test suite passes before any merge, push, or destructive action is offered.
  • Structured Decision Flow: Presents exactly four concise options (merge locally, push and create PR, keep as-is, discard) to avoid ambiguity.
  • Safe Execution & Cleanup: Performs git merges, pushes, PR creation via gh, branch deletion with typed confirmation for destructive actions, and conditional git worktree cleanup.
  • Use Case: A developer finishing a feature branch uses this Skill to validate tests, choose a safe integration path, and clean up local worktrees when appropriate.

Quick Start

Use the finishing-a-development-branch skill to verify tests and present merge, push/PR, keep, or discard options for 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 safely finalize a Git feature branch and merge it?

To finalize a Git feature branch, you need to verify tests pass, choose an integration path like merging locally or pushing a PR, and safely clean up the worktree to prevent accidental data loss.

What steps are required to clean up a git worktree after finishing development?

Cleaning up a git worktree after finishing development requires explicit delete confirmation to ensure no local changes are lost, safely removing the worktree only after the chosen merge or discard action is fully executed.

Can I create a GitHub pull request and verify tests before merging a branch?

Yes, you can create a GitHub pull request using gh commands after verifying that the project's test suite passes, ensuring the branch is validated before pushing it as a PR for integration.

What are my options for integrating a development branch into the base branch?

When integrating a development branch, you have four fixed options: merge locally into the base branch, push and create a pull request, keep the branch as-is for later work, or discard it entirely.

Does discarding a Git branch require explicit confirmation to prevent data loss?

Yes, discarding a Git branch requires typed confirmation for this destructive action, ensuring that developers explicitly acknowledge the permanent deletion of the branch and its associated worktree.