skills.rest
shmily1012
shmily1012COMMUNITY
Explore all skills by this author →
GitHub

finishing-a-development-branch

Present merge, pull request, keep, or discard options after tests pass.

1|1|Updated Dec 1, 2025
Search Tags:#git#workflow#pull-request#merge-strategy#branch-cleanup#finish-branch
One-click install
npx skills add https://github.com/shmily1012/AutoWriter --skill finishing-a-development-branch-shmily1012
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/shmily1012/AutoWriter/tree/main/.claude/skills/finishing-a-development-branch
Command: npx skills add https://github.com/shmily1012/AutoWriter --skill finishing-a-development-branch-shmily1012

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finishing a development branch is a common bottleneck: teams must decide how to integrate completed work safely after tests pass, choosing an optimal merge/PR/cleanup path to avoid drift, conflicts, or stale branches.

Core Features & Use Cases

  • Verify that tests pass before presenting options.
  • Determine the most appropriate base branch and merge strategy.
  • Offer four concrete actions: merge locally, push and create PR, keep as-is, or discard.
  • Cleanup worktrees and branches after an action.

Quick Start

After all tests pass, run this skill to select a merge, PR, keep, or discard path and finalize the development branch.

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

To finish a git development branch after tests pass, you select one of four explicit actions: merge locally, push and create a pull request, keep the branch as-is, or discard it. The workflow then performs post-action cleanup.

What is the best way to merge a feature branch into the correct base branch?▼

The best way to merge a feature branch is to first determine the correct base branch and apply an appropriate merge strategy. This ensures safe integration of completed work while preventing drift or conflicts.

Can I create a pull request automatically when my feature branch is ready?▼

Yes, when your feature branch is ready, you can choose the push and create PR action. This workflow presents this as one of four deterministic options after verifying tests pass.

How does branch cleanup work after merging a development branch?▼

Branch cleanup happens automatically after you select an action. Once you merge, create a PR, or discard your development branch, the workflow cleans up worktrees and branches to avoid stale references.

Why should I discard a git branch instead of keeping it?▼

You should discard a git branch when the work is no longer needed or tests fail. This workflow offers discarding as one of four explicit actions, removing unnecessary branches and cleaning the worktree.

Do I need to run tests before merging a git branch?▼

Yes, you must ensure tests pass before options are shown. This prerequisite guarantees that only verified, passing code is presented for integration against the main or master branch.

Related Skills

Explore More Software Engineering Skills→
WesleyMFrederickWesleyMFrederick

setting-up-implementation-worktree

Create a fresh git worktree with verified tests and dependencies.

Community
Advanced
Synaptic-Labs-AISynaptic-Labs-AI
71

worktree-cleanup

Remove a stale git worktree and its associated local branch.

Official
Advanced
aadorianaadorian

merge-changes

Merge a topic branch into its merge base branch with conflict resolution.

Community
Intermediate
ytqhytqh

finishing-a-development-branch

Integrate a finished development branch by choosing one of four Git workflow options.

Community
Basic