finishing-a-development-branch

Guide merge, PR, or cleanup options after verifying tests pass.

2|Updated Feb 7, 2026

Search Tags:#git #workflow #testing #cleanup #merge #branch-management #pull-request

Ready to run

npx skills add https://github.com/SamuelJennings/django-mvp --skill finishing-a-development-branch-samueljennings

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/SamuelJennings/django-mvp/tree/main/.github/skills/finishing-a-development-branch
Command: npx skills add https://github.com/SamuelJennings/django-mvp --skill finishing-a-development-branch-samueljennings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Core Features & Use Cases

Clear, structured end-to-end workflow for finalizing development branches
Supports four fixed outcomes: merge locally, push PR, keep branch, or discard
Includes verification of tests and safe cleanup steps

Quick Start

Run finishing-a-development-branch to complete the work by selecting one of four options after tests pass: merge locally, push and create a PR, keep the branch, or discard

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 merge a git development branch after all tests pass?▼

To merge a git development branch after tests pass, the workflow verifies your test suite, resolves the target base branch, and presents structured options to finalize the work via local merge, PR, branch retention, or discard.

What are the best git workflow options for finishing a completed branch?▼

The best git workflow options for finishing a completed branch include four deterministic outcomes: merge locally into the base branch, push and create a pull request, keep the branch active, or discard the work entirely.

How does branch cleanup work after a git merge or pull request?▼

Branch cleanup after a git merge or pull request removes the finalized development branch safely once the selected workflow outcome is executed, ensuring the repository stays organized without losing integrated work.

Do I need to verify tests before creating a pull request from a git branch?▼

You need to verify tests pass before creating a pull request from a git branch, as the workflow requires test verification as a prerequisite step before presenting options to push and create a PR.

Can I keep or discard a git branch instead of merging it?▼

You can keep or discard a git branch instead of merging it, as the workflow provides four fixed outcomes allowing you to retain the branch for future work or discard it after test verification.

How do I determine the correct base branch for a git merge?▼

To determine the correct base branch for a git merge, the workflow performs base-branch resolution automatically, identifying the appropriate target before guiding you through the final merge or PR creation step.