finishing-a-development-branch

Present merge, PR, or cleanup options after tests pass.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/randoneering/nix-flake-mirror --skill finishing-a-development-branch-randoneering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/randoneering/nix-flake-mirror/tree/main/home/programs/opencode/skills/finishing-a-development-branch
Command: npx skills add https://github.com/randoneering/nix-flake-mirror --skill finishing-a-development-branch-randoneering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams through the finalization of a development branch by presenting a concise set of merge, PR, or cleanup options after tests pass.

Core Features & Use Cases

  • Deterministic option prompts: presents exactly four options to resolve the development branch (merge locally, push with PR, keep as is, or discard).
  • Safety checks and cleanup: validates tests before proceeding and supports post-action cleanup, including worktree handling.
  • Use Case: When a feature is complete and you need a clear path to integrate or remove the branch, this Skill orchestrates the decision and execution.

Quick Start

Run the finishing-a-development-branch skill to review tests, choose an option, and apply the selected workflow.

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 automate Git branch cleanup after a feature is complete?

Automating Git branch cleanup is handled by presenting structured finalization options after tests pass, allowing you to discard, keep, merge locally, or push for a PR. The workflow executes the selected option and performs worktree cleanup automatically.

What is the best way to manage merge options for a finished development branch?

Managing merge options for a finished development branch is streamlined through deterministic option prompts. The system presents exactly four choices: merge locally, push with a PR, keep the branch as is, or discard it entirely.

How do I create a pull request automatically when my feature branch passes tests?

Creating a pull request automatically is supported by validating tests first, then offering a remote PR creation option. This coordinates the finalization decision across Git workflows and hosting platforms to push your feature branch safely.

Can I use this branch management workflow across different Git hosting platforms?

Using this branch management workflow across different Git hosting platforms is fully supported. The process applies to feature branches after all tests pass, coordinating end-to-end actions regardless of your specific remote repository provider.

When should I discard a development branch instead of merging it?

Discarding a development branch instead of merging is appropriate when feature work is abandoned or needs a clean reset. The workflow presents this as one of four deterministic options, ensuring safety checks pass before executing the branch cleanup.

Does this Git workflow require any specific dependencies to finalize a branch?

Finalizing a branch with this Git workflow requires no specific dependencies. It operates independently to apply safety checks, present merge or PR options, and execute optional worktree cleanup after your development tests pass.