finishing-a-development-branch

Guides Git users through finishing a development branch after tests pass.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/Xinm123/MyRecall --skill finishing-a-development-branch-xinm123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/Xinm123/MyRecall/tree/main/openrecall/.trae/skills/finishing-a-development-branch
Command: npx skills add https://github.com/Xinm123/MyRecall --skill finishing-a-development-branch-xinm123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps development teams finish a feature branch after all tests pass by guiding the final integration decision.

Core Features & Use Cases

  • Verify tests pass and determine the base branch.
  • Present four clear options: Merge locally, Push and create PR, Keep the branch, Discard and clean up.
  • Clean up worktrees after actions.

Quick Start

Run the finishing-a-development-branch skill after tests pass to choose the integration path.

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

To finish a development branch after tests pass, you choose from four integration options: merge locally, push and create a pull request, keep the branch, or discard and clean up the work.

What is the best way to decide between merging locally or creating a pull request?

The best way to decide between merging locally or creating a pull request is to evaluate your Git workflow needs and select from four explicit integration choices presented after verifying tests and determining the base branch.

How do I clean up Git worktrees after merging a feature branch?

To clean up Git worktrees after merging a feature branch, you follow the cleanup steps provided automatically once you select your preferred branch integration and finishing action.

When should I discard a feature branch instead of keeping it?

You should discard a feature branch instead of keeping it when the work is no longer needed, triggering an explicit cleanup option that removes the branch and its associated worktrees.

Does this branch finishing workflow require a specific base branch?

The branch finishing workflow does not require a hardcoded specific base branch; instead, it automatically determines the correct base branch for integration before presenting your merge or pull request options.