finishing-a-development-branch

Automates safe disposition choices for finished development branches.

Updated Mar 17, 2017
One-click install
npx skills add https://github.com/dfmonaco/dotfiles --skill finishing-a-development-branch-dfmonaco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/dfmonaco/dotfiles/tree/main/agents/.agents/skills/finishing-a-development-branch
Command: npx skills add https://github.com/dfmonaco/dotfiles --skill finishing-a-development-branch-dfmonaco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decide how to integrate, preserve, or discard verified work once implementation is complete. This skill guides completion of development work by presenting structured options for merge, PR, or cleanup.

Core Features & Use Cases

  • Verify Readiness: confirm current branch name, worktree state, latest verification evidence, and remote tracking status.
  • Determine Integration Context: identify the likely base branch, PR status, and linked worktree considerations.
  • Present Structured Options: provide a short list of concrete paths (merge locally, push and create/update PR, keep as-is, or discard) with an explicit recommendation.
  • Execute & Close Out: perform the chosen path safely when requested, and report resulting branch/PR/worktree state and next steps.

Quick Start

Use the finishing-a-development-branch skill to decide the safest next step for this 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 finish a development branch after passing tests?

The best way to finish a development branch is applying a verification checklist to determine integration context, then choosing a safe disposition path like merging locally, pushing for a pull request, holding, or discarding verified work.

How do I safely merge a verified git branch into the base branch?

Safely merge a verified git branch by confirming the worktree state and remote tracking status, identifying the likely base branch, and executing a local merge with safeguards to preserve or integrate completed implementation work.

When should I discard or hold a completed development branch instead of merging?

You should discard or hold a completed development branch when the implementation needs review, linked worktree considerations exist, or the PR status indicates unresolved issues, making merge unsafe and requiring preservation or cleanup instead.

Does finishing a git branch require a pull request or can I merge locally?

Finishing a git branch does not strictly require a pull request; you can merge locally if implementation is complete and verified, though pushing and creating a PR is recommended for structured code review and integration tracking.

What verification steps are needed before integrating development work?

Verification steps before integrating development work include confirming the current branch name, checking the worktree state, reviewing latest verification evidence, and validating remote tracking status to ensure tests pass and the base context is clear.