finish-branch

Automate pull request creation and branch cleanup by resetting working files to the main branch skeleton, verifying CI passes, and pushing the branch to open or ready a PR. This ensures a clean working tree and review-ready state without manual file restoration.

Transitioning a draft pull request to ready for review involves verifying CI passes, confirming adversarial review findings are resolved, and converting the draft state. The process detects existing PRs and safely shifts them to a review-ready status.

Verify CI and review readiness by executing build and test gates, auditing review state, and validating a clean working tree. This gate execution ensures all required checks pass and adversarial review findings are properly tracked before PR creation.

Yes, this branch wrap-up workflow requires the GitHub CLI to handle push operations, detect existing pull requests, and safely create new ones. Safe GitHub CLI handling ensures deterministic release completion during the end-of-branch finalization.

Agent working files show up in the final diff because they were not reset to the main branch skeleton before pushing. Restoring skeleton files while keeping branch-specific audit state separate prevents unwanted files from entering the PR.

You should not use automated branch finalization when your working tree has uncommitted changes or CI checks are failing. The process requires a clean working tree and successful build and test gate execution to guarantee a deterministic release.