finishing-a-development-branch

Verify tests and guide branch merge, PR, or discard decisions.

3|Updated Jun 3, 2022
One-click install
npx skills add https://github.com/Hohlas/SoSimple --skill finishing-a-development-branch-hohlas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/Hohlas/SoSimple/tree/main/.kilocode/skills/finishing-a-development-branch
Command: npx skills add https://github.com/Hohlas/SoSimple --skill finishing-a-development-branch-hohlas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides engineering teams to properly close a feature or development branch by ensuring tests pass, identifying the correct base branch, presenting standardized merge options, and cleaning up working copies.

Core Features & Use Cases

  • Verify tests pass across the project before merging or PR creation.
  • Determine base branch and align workflow for consistent merges.
  • Present exactly four options to standardize handoffs: merge locally, push and create PR, keep branch as-is, or discard.
  • Clean up worktrees and branches after completion to avoid drift.

Quick Start

Run this skill after tests pass to guide the finalization of a development branch by selecting a merge/PR path and performing cleanup.

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 development branch before merging?

To finalize a development branch safely, the workflow enforces passing tests, identifies the base branch, presents deterministic merge options, and executes cleanup steps to prevent branch drift.

What are the standard options for finishing a feature branch in Git?

The standard options for finishing a feature branch are merging locally, pushing to create a PR, keeping the branch as-is, or discarding it entirely to standardize handoffs.

Do I need to run tests before creating a PR or merging a branch?

Yes, this workflow enforces that tests must pass before any merge or PR creation is allowed, ensuring the base branch remains stable and preventing broken feature handoffs.

How do I clean up Git worktrees and branches after a merge?

To clean up after a merge, the workflow guides you through removing the completed development branch and cleaning up the associated worktrees to avoid local repository drift.

How does identifying the base branch improve Git workflow merge decisions?

Identifying the base branch aligns the workflow for consistent merges by ensuring the development branch targets the correct integration point, preventing accidental merges into the wrong target.