finishing-a-development-branch

Automate Git branch cleanup by enforcing mandatory test execution before providing a structured integration workflow. This standardizes branch completion by verifying your test suite and guiding you through merge, PR, keep, or discard options.

Managing worktree cleanup requires explicit confirmation to prevent accidental data loss during branch completion. The workflow ensures worktrees are only removed when appropriate, standardizing the lifecycle completion of development branches.

A structured workflow handles completed Git feature branches by presenting a four-option menu for integration. It enforces test verification and applies safety guardrails to prevent accidental deletion before merging or creating a pull request.

Yes, you can use local shell commands to verify tests before creating a Git pull request. The workflow requires access to local shell commands for Git operations and project-specific test runners to enforce mandatory test execution.

Safety guardrails prevent accidental data loss by requiring explicit confirmation for branch deletion. This ensures that worktrees are only removed when explicitly appropriate, securing your codebase during the branch completion process.