skills.rest
m16khb
m16khbCOMMUNITY
Explore all skills by this author →
GitHub

finishing-a-development-branch

Run the test suite and present four options for merging, PR, keeping, or discarding a branch.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill verifies tests and presents structured options for merging, PRs, or cleanup after development.

Core Features & Use Cases

  • Test verification: Run the test suite to confirm green status.
  • Structured options: Provide four clear next steps for merge vs PR vs keep vs discard.
  • Cleanup flows: Optional worktree cleanup after finishing.
  • Usage Scenario: After features pass tests, decide merge or PR workflow.

Quick Start

Run the test suite, then choose between merge locally, create PR, keep as-is, or discard.

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 decide whether to merge, create a pull request, or discard a development branch after tests pass?▼

After tests pass, this workflow presents four options: merge locally to integrate immediately, push a pull request for review, keep the branch for later use, or discard the work entirely. Choose based on your team's review requirements and integration timing.

What should I do before finishing a development branch?▼

Run your test suite to verify all tests pass. This confirms the branch is stable and ready for integration. Only proceed to merge, PR, or cleanup decisions after tests succeed.

Can I clean up my worktree after finishing a branch?▼

Yes. After selecting your integration option—merge, PR, keep, or discard—the workflow performs cleanup of the worktree to remove temporary files and reset your environment.

How do I know which base branch to merge into?▼

The workflow determines your base branch automatically based on your repository configuration. This ensures the merge targets the correct branch for your integration decision.

What's the best way to handle feature branches once development is complete?▼

Complete feature branches with passing tests benefit from structured integration decisions. This workflow guides you through merging locally, requesting review via PR, preserving the branch, or safely discarding work.

Related Skills

Explore More Software Engineering Skills→
TomekNoconTomekNocon

check-and-commit

Run build, generation, i18n, typecheck, unit tests, and app build checks before committing and pushing.

Community
Advanced
sumrae412sumrae412
2

finishing-a-development-branch

Verify tests and present Git branch integration options for merging or cleanup.

Community
Intermediate
Neuron-Mr-WhiteNeuron-Mr-White
56

worktree-merge

Merge worktree branches into the main branch with context gathering and conflict resolution.

Community
Intermediate
drndrn
23

merge

Merge the current Git branch into master via GitHub Pull Request.

Community
Advanced