finishing-a-development-branch

Verify tests and present four Git integration options for a finished branch.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/tense-i/stock-market-simulator --skill finishing-a-development-branch-tense-i
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/tense-i/stock-market-simulator/tree/main/skills/finishing-a-development-branch
Command: npx skills add https://github.com/tense-i/stock-market-simulator --skill finishing-a-development-branch-tense-i

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guide completion of development work by presenting clear options and handling chosen workflow.

Core Features & Use Cases

  • Verifies tests pass before presenting a workflow to integrate changes.
  • Presents four explicit options: merge locally, push and create PR, keep the branch as-is, or discard the work.
  • Includes guidance for identifying a base branch and performing cleanup after the chosen path.

Quick Start

Use this skill to decide how to integrate completed work by verifying tests, selecting a merge/PR/cleanup option, and performing optional cleanup.

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 and choose between a local merge or a pull request?▼

Finalizing a development branch involves verifying tests pass and then selecting from explicit integration options: merge locally, push and create a pull request, keep the branch, or discard the work entirely.

What is the best workflow to merge a finished Git branch safely?▼

A safe Git branch merge workflow verifies tests before presenting integration options and performs optional cleanup after the chosen path, ensuring deterministic results for local merges or pull requests.

Can I discard a development branch after tests pass without merging it?▼

Yes, you can discard a development branch after tests pass. The workflow presents discarding the work as one of four explicit integration options alongside merging, creating a pull request, or keeping it.

How do I identify the base branch before creating a pull request?▼

Identifying a base branch before creating a pull request is part of the workflow guidance provided when finalizing a development branch, ensuring changes integrate into the correct target.

Does this branch cleanup workflow run tests before allowing a merge?▼

Yes, the branch cleanup workflow verifies that tests pass before presenting any merge, pull request, keep, or discard options, ensuring only validated code proceeds through the integration process.