finishing-branch

What problem does it solve?

Automate finishing a development branch after all tasks are complete and tests pass, providing clear integration options and safe cleanup decisions.

Core Features & Use Cases

• Verification-driven finish: Confirms all tasks are complete and tests pass before any integration action.
• 4-option governance: Presents exactly four integration choices (merge locally, create PR, keep branch, discard) and follows a strict decision flow.
• Safe cleanup and governance: Manages worktrees and branch deletion with explicit confirmations to prevent data loss.
• Use Case: A completed feature branch can be finished by choosing between merging into main, opening a PR, keeping for later review, or discarding if abandoned.

Quick Start

1. Run TaskList to confirm all tasks show status completed.
2. Run the project’s test command (e.g., go test ./..., npm test, pytest) to ensure all tests pass.
3. Determine the base branch with git merge-base HEAD main (or master) to identify the integration base.
4. Run gambit:finish to begin the 6-step process and follow the prompts to select one of the four options.