skills.rest
bluefishs
bluefishsCOMMUNITY
Explore all skills by this author →
GitHub

finishing-a-development-branch

Validate tests and guide merge, PR, keep, or discard decisions on a feature branch.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finalize development work after implementation is complete and tests pass by offering a structured set of integration options (merge locally, push a PR, keep the branch, or discard and clean up).

Core Features & Use Cases

  • Verify tests pass before offering options to ensure safety.
  • Determine the base branch and present four explicit outcomes: merge locally, push a PR, keep as-is, or discard.
  • Clean up worktrees automatically after completing a chosen path.

Quick Start

Use the finishing-a-development-branch skill after all tests pass to present clear integration decisions and perform 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 safely finish a development branch and merge changes in git?▼

Tests must pass before it presents integration options. It validates your suite, determines the base branch, and offers explicit outcomes: merge locally, push a PR, keep the branch, or discard and clean up worktrees.

What is the best way to clean up feature branches after development?▼

The best way to clean up feature branches is to select an explicit finish option. After choosing to merge, push a PR, or discard, the workflow automatically cleans up worktrees to maintain a tidy environment.

How do I create a pull request after verifying tests on a feature branch?▼

You create a pull request after verifying tests by selecting the PR creation option. The process determines the base branch and guides the push, followed by optional worktree cleanup to finalize the action.

Can I discard local development work and clean up the worktree automatically?▼

Yes, you can discard development work and clean up worktrees automatically. By selecting the discard option after test verification, the workflow removes the finished feature branch and cleans the associated worktree.

Does finishing a development branch require tests to pass before merging?▼

Yes, finishing a development branch requires tests to pass before offering options. This ensures safe, repeatable workflows for local merges, PR creation, keeping the branch, or discarding work.

When should I keep a development branch instead of merging or discarding it?▼

You should keep a development branch when integration is premature. Selecting the keep-as-is option preserves the worktree without merging or discarding, leaving the feature available for later finalization.

Related Skills

Explore More Software Engineering Skills→
conejoRojoconejoRojo

finishing-a-development-branch

Verify test suites and manage branch integration workflows with git.

Community
Intermediate
wilfozwilfoz

cloudflare-deploy

Deploy and manage Cloudflare Workers, Pages, R2, and D1 resources via CI/CD pipelines.

Community
Intermediate
philoserfphiloserf
13

git-workflow

Automate Git workflows with atomic commits, branch management, and PR creation.

Community
Advanced
UniClipboardUniClipboard
1.5k

finishing-a-development-branch

Offer merge, PR, keep, or discard options after tests pass.

Official
Advanced