superpowers-finishing-a-development-branch

Finishing a git branch after tests pass involves verifying the test suite, detecting the repository environment, and presenting consistent options to merge locally, push a pull request, or execute cleanup.

Finalizing a git worktree with a named branch or detached HEAD is supported. The process detects the repository state and adapts its options to support normal repos, named-branch worktrees, and detached HEAD workflows.

The best way to merge or push a pull request from a development branch is to use a four-option decision flow that verifies tests first, then executes the chosen finalization path with optional worktree management and automatic cleanup.

Yes, finishing a branch automatically cleans up the local worktree. After executing the chosen finalization action, such as a local merge or pull request push, the process performs post-work cleanup to remove unnecessary worktree artifacts.

Verifying tests before merging a development branch prevents broken merges. The finalization flow checks that tests pass successfully before presenting execution options, ensuring only stable code is merged or submitted as a pull request.