superpowers-finishing-a-development-branch

Finishing a development branch is streamlined by verifying tests, detecting the base branch, and choosing from four options: merge locally, push and create a PR, keep as-is, or discard. This ensures safe integration and deterministic execution for your workflow.

Before merging a git feature branch, you should run test validation as a guardrail step. This skill specifies test verification as a prerequisite step to ensure safe integration before selecting a final path like a local merge or pull request.

Yes, this branch cleanup workflow supports git worktrees by performing optional worktree cleanup after executing your chosen integration option. This ensures your multi-branch environment remains tidy after finishing development work.

To discard a feature branch safely, the workflow presents discarding as one of four fixed options after test validation. Selecting this option triggers deterministic execution steps to remove the branch and perform optional worktree cleanup.

Yes, you can use this skill for local merges in a multi-branch environment. It applies to branching workflows by detecting the base branch and guiding the local merge process with clear, actionable steps and guardrails.

A guided workflow for pull request creation prevents integration errors by enforcing test validation and base-branch detection before pushing. It provides deterministic execution steps and optional worktree cleanup, ensuring a clean handoff that manual commands often miss.