finishing-a-development-branch

To finalize a git branch, you need to verify tests pass and then choose a deterministic integration path. This skill automates branch finalization by verifying tests and presenting four concrete options for merging, creating a pull request, keeping, or discarding the feature branch.

The best way to clean up feature branches is to execute safe cleanup steps after integration. This skill guides you through merge, PR, or cleanup decisions and performs safe deletion of worktrees and branches once the chosen action is complete.

Creating a pull request after tests pass requires determining a suitable base branch and selecting the PR action. This skill verifies your tests, identifies the base branch, and offers a specific pull request option among its four deterministic choices.

Yes, you can automate the git workflow for wrapping up development work by running this skill after tests pass. It ensures an auditable wrap-up by automating test verification and guiding you through explicit merge, PR, or cleanup actions.

To discard a git feature branch safely, you need a workflow that offers explicit cleanup choices. This skill presents discarding the feature as one of four concrete actions and executes safe cleanup of worktrees and branches when selected.

Yes, finishing a development branch requires passing tests before merging. This skill verifies that tests pass before offering any options to integrate, keep, or discard the work, ensuring a clean and auditable wrap-up.