skills.rest
mealpac
mealpacCOMMUNITY
Explore all skills by this author →
GitHub

finishing-a-development-branch

Apply a structured merge, PR, or cleanup workflow after tests pass.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides completion of development work by presenting clear, deterministic options for merge, PR, or cleanup once tests pass.

Core Features & Use Cases

  • Test verification: ensures the feature branch passes the test suite before any integration decision.
  • Base-branch resolution: detects the appropriate base branch (main or master) and confirms the correct target.
  • Structured options: presents four explicit outcomes (merge locally, push PR, keep the branch, discard) to finish the workflow with minimal ambiguity.
  • Auditable cleanup: provides reproducible commands for merging, PR creation, branch deletion, or worktree cleanup.

Quick Start

Review tests, choose one of the four options, and execute 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 safely finish a git development branch after tests pass?▼

To finish a development branch, verify passing tests, determine the correct base branch, and choose from explicit outcomes like local merge, PR push, branch retention, or discard to ensure safe integration.

What's the best way to determine the target base branch for a git merge?▼

The workflow resolves the base branch by detecting whether main or master is the appropriate target, ensuring your development branch integrates cleanly into the correct repository history.

How do I clean up a feature branch after merging it into the main branch?▼

Cleanup involves executing reproducible commands for branch deletion or worktree removal after the merge is complete, ensuring the repository remains auditable and free of stale branches.

What are the options for completing work on a development branch?▼

Structured options for completing work include merging locally, pushing a pull request, keeping the branch for further development, or discarding the changes entirely.

Can I create a pull request directly through this development workflow?▼

Yes, pushing a pull request is one of the four explicit outcomes provided to finish the workflow, giving you reproducible commands to create the PR and safely integrate your feature branch.

Why does the workflow require test verification before merging a branch?▼

Test verification is enforced before any integration decision to guarantee the feature branch passes the test suite, preventing broken code from entering the base branch and ensuring safe completion.

Related Skills

Explore More Software Engineering Skills→
SamuelJenningsSamuelJennings
2

finishing-a-development-branch

Guide merge, PR, or cleanup options after verifying tests pass.

Community
Advanced
nikhilsitaramnikhilsitaram
89

pr-merge

Merge reviewed GitHub pull requests and clean up branches and worktrees.

Community
Advanced
LuizfbmLuizfbm
1

finishing-a-development-branch

Verify tests and merge feature branches with git worktree cleanup.

Community
Advanced
791994545791994545
4

finishing-a-development-branch

Finish a git development branch with test verification and cleanup.

Community
Intermediate