finishing-a-development-branch

To automate finishing a git development branch, this skill verifies your tests pass, detects the base branch, and presents explicit options to merge, create a pull request, keep, or discard the work. It then executes the chosen workflow and cleans up the worktree.

Merging a feature branch offers four explicit options: merging locally back to the base branch, pushing and creating a pull request, keeping the branch as-is, or discarding the work entirely. The chosen action is then executed automatically with safety guardrails.

Yes, you can create a pull request directly from a local git workflow by selecting the push and create PR option presented after tests pass. The skill determines the appropriate base branch and handles the push action to initiate the pull request process.

Worktree cleanup when discarding a development branch includes safety checks to prevent data loss. After you choose to discard the work or complete a merge, the skill performs optional worktree cleanup to ensure a clean repository state.

Verifying tests before merging a git feature branch ensures the branch is stable before completion. This skill runs the project's test suite or validates test results as a prerequisite to presenting the four structured options for finalizing the development workflow.

Yes, finishing a development branch works with both main and master base branches. The skill automatically detects the appropriate base branch for merging or creating a pull request, ensuring the deterministic handoff process applies across standard Git workflows.