finishing-a-development-branch

To finish a development branch after tests pass, this skill guides you through base-branch detection and presents four structured options for merge, PR, or cleanup to ensure a clean integration path.

The best way to clean up a Git worktree after merging is selecting a structured completion option that handles worktree management and follow-up cleanup actions, finalizing the feature integration safely.

No, you cannot use this branch management workflow without a Git-enabled environment, as the skill requires runnable tests and explicit guardrails to prevent destructive actions during integration.

Base-branch detection works by identifying the source branch to determine the correct integration path, ensuring your merge, pull request, or cleanup actions target the appropriate base branch.

The structured options for integrating a completed Git branch are four distinct choices presented after tests pass, covering merge, pull request, and cleanup actions to keep branch management decisions unambiguous.

Finishing a development branch requires passing tests first to verify your implementation works, preventing the introduction of failing changes into the base branch during the Git integration process.