finishing-a-development-branch

Completes a git feature branch by verifying tests and executing chosen action.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Berkay2002/skills --skill finishing-a-development-branch-berkay2002
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/Berkay2002/skills/tree/main/skills/finishing-a-development-branch
Command: npx skills add https://github.com/Berkay2002/skills --skill finishing-a-development-branch-berkay2002

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides the finalization of a development branch by ensuring tests are verified, offering a fixed set of integration choices, and preventing accidental loss of work or premature merges.

Core Features & Use Cases

  • Test Verification: Runs or instructs verification of the project's test suite and halts if failures are present to avoid introducing regressions.
  • Structured Decision Flow: Presents exactly four concise options (merge locally, push & create PR, keep as-is, discard) and executes the chosen git workflow with required confirmations.
  • Worktree & Cleanup Management: Detects and removes git worktrees when appropriate and enforces typed confirmation for destructive actions.
  • Use Case: After finishing a feature and ensuring tests pass, use this Skill to choose whether to merge into the base branch, open a PR for review, preserve the branch for later work, or safely discard it with confirmation.

Quick Start

Use the finishing-a-development-branch skill to verify tests, select one of the four options (merge, create PR, keep, or discard), and perform the corresponding git and worktree actions with required confirmations.

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 after tests pass?

To finalize a git feature branch, verify your test suite passes, then choose to merge locally, push for a pull request, keep the branch, or discard it with required confirmation prompts.

What is the best way to merge a development branch into a base branch?

Merging a development branch involves verifying tests, determining the correct base branch, and executing local git merge commands while ensuring worktree cleanup is handled properly.

How does git worktree cleanup work when discarding a branch?

Git worktree cleanup during branch discarding requires typed confirmation for destructive actions, safely removing the worktree and deleting the branch to prevent accidental work loss.

Can I create a pull request directly from a local feature branch?

Yes, you can push the branch and create a pull request after passing test verification, which is one of the four structured options provided for git branch finalization.

Why should I verify tests before merging a git branch?

Test verification before merging prevents introducing regressions into the base branch, halting the finalization process if failures are present to ensure code stability.

When should I keep a git development branch instead of merging or discarding it?

Keep a git development branch when implementation needs later work; this option preserves the branch as-is without merging or deleting, allowing continued development.