finishing-a-development-branch

After tests pass, finishing a development branch means verifying stability and choosing between four options: merge locally, push and create a pull request, keep the branch as-is, or discard it entirely. The Skill presents these structured options, executes your choice, and cleans up worktrees automatically.

After completing work on a development branch, clean up by removing worktrees and branches appropriately to your chosen path—local merge, PR submission, retention, or discard. This prevents stale branches and orphaned worktrees from cluttering your repository.

Yes. The Skill automates branch completion by running test verification first, then presenting exactly four completion paths: local merge to the base branch, push and open a PR, keep the branch unchanged, or clean up and discard. You select the option that fits your workflow.

Test verification happens automatically when finishing a development branch. The Skill runs your test suite to confirm stability before presenting merge or cleanup options, ensuring only verified code moves forward in your CI/CD workflow.

When you complete branch finalization, worktrees are cleaned up automatically as part of the chosen action—whether you merge locally, submit a PR, retain the branch, or discard it. This ensures your working directory stays organized without orphaned worktrees.

Yes. Finishing a development branch integrates into standard CI/CD workflows by verifying tests pass, determining your base branch, offering four completion options, executing the selected action, and performing required cleanup—all designed for typical merge or PR-based deployment pipelines.