superpowers:finishing-a-development-branch

To safely merge a git branch, you need an automated workflow that enforces test verification before integration. This ensures all tests pass and prevents merging broken code by standardizing the branch completion process.

The best way to clean up git worktrees is using environment-aware detection to safely remove them only when managed by the system. This prevents leaving behind messy, redundant worktrees after branch integration.

You can automate git branch finalization by running a standardized completion workflow that requires a valid test suite. It enforces automated verification, blocking integration steps until all tests pass successfully.

Yes, you can create a pull request instead of a local merge. The workflow provides structured options through a menu-driven interface, allowing you to choose between merging locally, creating PRs, or discarding work safely.

Yes, you need git command-line access and a valid test suite to finalize development branches. These prerequisites are required to verify code integrity and manage the lifecycle of git worktrees before branch deletion.