finishing-a-development-branch

Selects a finalization path for a clean, tested development branch.

1|1|Updated May 3, 2026

Search Tags:#testing #development #integration #merge #branch #guardrails #pull-request

Ready to run

npx skills add https://github.com/matt-riley/agent-skills --skill finishing-a-development-branch-matt-riley

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/matt-riley/agent-skills/tree/main/skills/finishing-a-development-branch
Command: npx skills add https://github.com/matt-riley/agent-skills --skill finishing-a-development-branch-matt-riley

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Efficiently decides the best path to finalize a completed development branch after all changes and tests pass.

Core Features & Use Cases

Verifies worktree cleanliness and test status before action.
Presents four integration options: merge locally, push and create a PR, keep the branch, or discard.
Provides guardrails and post-action cleanup/validation guidance for reliable handoff.

Quick Start

Announce and initiate the finishing-a-development-branch workflow to finalize a completed feature branch.

Frequently Asked Questions about finishing-a-development-branch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What's the best way to finalize a completed development branch after tests pass?▼

Finishing a development branch involves choosing between merging locally, creating a pull request, keeping the branch, or discarding it. The optimal path depends on your team's integration workflow and whether you need a peer review before finalizing the merge.

How do I merge a feature branch locally and ensure the worktree is clean?▼

To merge a feature branch locally, first verify your worktree is clean and all local tests pass. This ensures a repeatable integration process by enforcing guardrails before allowing a local merge commit to be created.

When do I need to create a pull request instead of merging a branch myself?▼

You need to create a pull request when your workflow requires peer review or automated integration checks before finalizing a development branch. This path pushes your changes remotely, enabling CI guardrails and team validation prior to the merge.

Can I keep a development branch active after changes are finished?▼

Yes, you can keep a development branch active after changes are finished. This option preserves the work without merging or discarding, which is useful if you need to pause integration or maintain the branch for future updates.

How do I clean up a feature branch after merging or discarding changes?▼

After merging or discarding changes, post-action cleanup involves validating the integration and removing the finished feature branch. This ensures a reliable handoff and maintains a clean worktree for future development work.

Why does my feature branch need to pass local tests before integration options are presented?▼

Your feature branch needs to pass local tests to satisfy integration guardrails before any finalization options are presented. This requirement prevents broken code from being merged or pushed, ensuring a reliable and repeatable handoff process.