finishing-a-development-branch

Test verification is a mandatory first step in branch completion. Run your project's test suite to ensure all tests pass before proceeding to merge, create a pull request, or clean up your branch. This prevents broken code from reaching your main branch.

After tests pass, you have four explicit options: merge the branch locally into the base branch, create a pull request for review, keep the branch for later, or discard the work entirely. The skill guides you through each path and handles the corresponding Git and worktree operations.

Branch completion automates cleanup by detecting your chosen integration option—merge, PR, keep, or discard—and then deletes the Git branch or removes the worktree accordingly. This ensures your workspace stays organized without manual git commands.

Yes, this workflow applies to feature branches in standard Git workflows. It automatically detects a valid base branch, runs tests, presents integration options, and executes your choice with built-in cleanup, making it suitable for typical development lifecycles.

Test success is enforced before progression. If tests fail, the workflow halts and does not offer merge, PR, or cleanup options until all tests pass, protecting your main branch from broken code.