finishing-a-development-branch

Verify tests pass, then present merge, PR, keep, or discard options.

6|Updated Mar 24, 2019
One-click install
npx skills add https://github.com/rafifos/dotfiles --skill finishing-a-development-branch-rafifos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/rafifos/dotfiles/tree/main/dot_agents/skills/finishing-a-development-branch
Command: npx skills add https://github.com/rafifos/dotfiles --skill finishing-a-development-branch-rafifos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guide engineers to finalize development work by ensuring tests pass and selecting a clear merge or cleanup path.

Core Features & Use Cases

  • Verify tests before completion to prevent broken integration.
  • Detect a base branch (e.g., main/master) and align the feature branch accordingly.
  • Present exactly four structured options: Merge back to base locally, Push and create a PR, Keep the branch as-is, or Discard this work.
  • Execute the chosen option and optionally clean up the worktree to return to a clean state after completion.
  • Use case: after implementing a feature on a development branch, run this workflow to determine the preferred integration path and perform any necessary cleanup.

Quick Start

Initiate the finishing-a-development-branch workflow to guide you through completing work after tests pass.

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 finalize a development branch after tests pass?

To finalize a development branch after tests pass, you can choose from four structured options: merge locally to the base branch, push and create a PR, keep the branch as-is, or discard the work entirely.

What are the options for finishing a feature branch ready for merge?

The options for finishing a feature branch include merging back to the base branch locally, pushing to create a PR, keeping the branch as-is, or discarding the work, followed by optional worktree cleanup.

How does base-branch detection work when completing development work?

Base-branch detection works by identifying the main or master branch to align your feature branch correctly before execution, ensuring the merge or PR creation targets the appropriate integration point.

Can I clean up my worktree after merging a feature branch?

Yes, you can clean up your worktree after merging a feature branch; the workflow executes your chosen completion option and performs optional worktree cleanup to return your environment to a clean state.

Does this workflow verify tests before creating a PR?

Yes, this workflow verifies that tests pass before presenting completion options, preventing broken integration and ensuring your feature branch is safe for PR creation or a local merge.

When should I discard my development work instead of merging?

You should discard development work instead of merging when the feature is obsolete or testing fails irrecoverably; the workflow offers discarding as one of four explicit paths to finalize the branch.