skills.rest
liamtran96
liamtran96COMMUNITY
Explore all skills by this author →
GitHub

finishing-a-development-branch

Present four integration options after tests pass for a development branch.

Updated Jan 30, 2026
Search Tags:#git#workflow#testing#merge#pull-request#development-branch#finishing
One-click install
npx skills add https://github.com/liamtran96/msm-car-booking --skill finishing-a-development-branch-liamtran96
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/liamtran96/msm-car-booking/tree/main/.claude/skills/finishing-a-development-branch
Command: npx skills add https://github.com/liamtran96/msm-car-booking --skill finishing-a-development-branch-liamtran96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the finalization of a development branch by presenting a structured set of options after tests pass.

Core Features & Use Cases

  • Structured decision: after tests pass, present four concrete options for integrating work.
  • Safety checks: ensures tests pass before options are offered.
  • Workflow automation: helps teams standardize end-of-feature steps.

Quick Start

Announce at the start: 'I'm using the finishing-a-development-branch skill to complete this work.' Step 1: Verify tests pass for the current branch. Step 2: Determine the base branch (e.g., main or master). Step 3: Present exactly four options and wait for selection. Step 4: Execute the chosen option (merge locally, push PR, keep as-is, or discard). Step 5: Cleanup worktree if applicable.

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

Finalizing a development branch requires verifying tests pass, determining the base branch, and selecting from structured options like local merge, push and PR, keep, or discard.

What's the best way to merge a completed feature branch locally?▼

Merging locally is one of four structured options presented after tests pass, requiring you to identify the base branch (main or master) and execute explicit git commands for integration.

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

Discarding is a supported option presented after tests pass, allowing you to abandon the development branch work and clean up the worktree if applicable.

Why do I need tests to pass before creating a pull request?▼

Tests must pass as a safety check before integration options are offered, ensuring completed feature work is verified before executing a push and PR or local merge workflow.

Does this workflow support keeping a development branch without merging?▼

Keeping the branch as-is is one of the four explicit options presented after test verification, allowing you to defer the final integration decision without discarding the work.

What is the standard workflow for finishing a development branch?▼

The workflow involves announcing the skill, verifying tests, determining the base branch, selecting one of four integration options, executing git commands, and cleaning up the worktree.

Related Skills

Explore More Software Engineering Skills→
RamblurrRamblurr

Finishing a Development Branch

Verifies tests, formatting, and linting before creating a Pull Request.

Community
Intermediate
DecentralizedGeoDecentralizedGeo
1

finishing-a-development-branch

Verify tests and guide Git merge decisions with worktree cleanup.

Official
Advanced
cwilliams5cwilliams5
1

clean-all

Delete all non-main Git branches locally and remotely, prune stale references, and remove worktrees.

Community
Intermediate
GaryOcean428GaryOcean428

finishing-a-development-branch

Verify project tests and present Git integration options for branch completion.

Community
Intermediate