finishing-a-development-branch

To finalize a git feature branch, the skill verifies tests, detects the base branch, and presents four explicit options: merge locally, push and create a pull request, keep the branch, or discard it. This ensures safe completion with structured prompts and automated cleanup.

Automating git branch cleanup involves choosing a discard or merge option from a structured prompt after tests pass. The workflow detects the base branch and performs the chosen action, applying automated cleanup to remove the finished feature branch safely.

To verify tests before creating a pull request, run a finalization workflow that checks test status and identifies the base branch. Once tests pass, it offers an explicit option to push the feature branch and create a PR directly.

Yes, you can merge a feature branch locally instead of pushing a PR. The workflow detects your base branch and provides an explicit local merge option alongside the push, keep, and discard choices after verifying tests.

Yes, this git branch management workflow works with custom base branches. It detects the base branch automatically and can be tuned to project-specific base branches for typical git workflows before offering merge or pull request options.

If you want to keep your git feature branch instead of merging it, select the keep branch option. The workflow presents this as one of four explicit choices after verifying tests, ensuring the branch remains intact without forced cleanup.