finishing-a-development-branch

To finalize a Git development branch, this Skill verifies your tests pass, detects the repository environment, and presents structured options to merge locally, push a pull request, keep the branch, or discard it. It then executes the chosen workflow and cleans up the workspace safely.

When finishing development work in a detached HEAD state, the Skill detects the specific environment scenario and tailors the completion options accordingly. It ensures safe handoff by presenting appropriate merge, pull request, or cleanup choices suited for detached HEAD repositories.

Yes, you can choose between a local merge and a pull request. The Skill presents a structured decision flow offering four concrete options: merge locally, push a pull request, keep the branch as-is, or discard the work entirely.

Test verification validates that the project's tests pass before offering any branch completion options. This ensures that only successfully tested code proceeds to the merge, pull request, or cleanup workflow.

Yes, this branch management workflow supports normal Git repos and performs necessary workspace cleanup only when appropriate. It preserves host environments as needed while finalizing your finished feature branch.

You should avoid using automated Git merge and cleanup options if your project's tests have not passed, as the Skill requires test verification before presenting completion workflows. It is designed specifically for finished feature branches in standard Git workspaces.