skills.rest
swissonid
swissonidCOMMUNITY
Explore all skills by this author →
Website𝕏@swissonidGitHub

finishing-a-development-branch

Validate tests and guide merge, PR, or cleanup workflows for git branches.

Updated May 19, 2026
Search Tags:#git#cleanup#worktree#merge#branch-management#pull-request#finish
One-click install
npx skills add https://github.com/swissonid/pi-superpowers --skill finishing-a-development-branch-swissonid
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/swissonid/pi-superpowers/tree/main/skills/finishing-a-development-branch
Command: npx skills add https://github.com/swissonid/pi-superpowers --skill finishing-a-development-branch-swissonid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides the safe completion of development work by presenting structured options after all tests pass, ensuring predictable merge, PR, or cleanup decisions.

Core Features & Use Cases

  • Verifies test results before finalizing work
  • Detects repository state to tailor available options (normal, named worktree, or detached HEAD)
  • Provides a deterministic path for merge, PR, keep, or discard with optional workspace cleanup

Quick Start

Run the finishing flow on your completed branch, verify tests pass, and select one of the four structured options.

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 clean up a git worktree after merging a feature branch?▼

To safely clean up after a git branch merge, verify tests pass, detect your repository state, and select from structured options to merge, keep, or discard the worktree workspace.

What is the best way to automate git branch cleanup after tests pass?▼

Automating git branch cleanup after tests pass involves validating test results, determining the base branch, and presenting a deterministic path to finalize the merge or discard the development work.

How do I finish a development branch when I am in a detached HEAD state?▼

Finishing a development branch in a detached HEAD state requires detecting the repository environment to tailor available options, ensuring consistent merge, PR, or discard decisions across CI workflows.

Can I create a pull request automatically after my repository tests pass?▼

Yes, you can create a pull request after tests pass by selecting the PR option from a fixed set of structured workflows presented during the branch completion process.

Does git branch management work differently inside a CI workflow?▼

Git branch management inside a CI workflow requires assessing the repository state, such as normal branches, named worktrees, or detached HEAD, to present consistent options for merge, PR, or discard.

Why should I verify tests before finalizing a git merge or discard workflow?▼

Verifying tests before finalizing a git merge or discard workflow ensures predictable completion of development work, preventing broken code from being integrated into the base branch.

Related Skills

Explore More Software Engineering Skills→
rhussrhuss
107

verification-before-completion

Run npm, pytest, and go tests to verify spec compliance before completion.

Community
Basic
takemi-ohamatakemi-ohama

cherry-pick-pr

Create a cherry-pick pull request from a feature branch to a base branch.

Community
Intermediate
vitaliytvvitaliytv

n-worktree

Automate git-worktree creation and management for parallel development workflows.

Community
Intermediate
EpiphyticEpiphytic
7

merge

Commit staged changes, rebase branches, and run workmux merge workflows.

Official
Intermediate