PR
Publish a change as a PR and watch it to ready. Start from a change or an existing PR. Leave one PR at a verified head, with its checks and feedback accounted for. You are done when the PR is ready or a finished draft, or you have named exactly what blocks it. A request for text alone is done when you return the text.
Review Sweep fixes findings. Merge lands
PRs, so send a merge request there, including /pr yolo. A draft request wins over /pr yolo. gh-stack owns stack operations.
Resolve the PR or branch, its immediate base, and what was asked. Leave unrelated local work out of commits, review inputs, and fixes.
Write the title and body
Use PR body. Return the text locally unless asked to update the remote description. Writing text commits and pushes nothing.
Publish
Watching an existing PR starts at step 4.
- Prepare it. Run Show, Don't Tell on the complete diff against the immediate base, including docs-only changes, unless earlier evidence covers this change. Then commit.
- Get it reviewed. Run Review Fix Loop on the committed head. A new head of reviewed work, such as after a base update or restack, is a repair pass. Earlier review of this exact commit finishes it and posts the status. Continue once review and verification pass.
- Publish it. Follow publish. Publish ready for review unless the user asks for a draft. In T3, link each PR you create, push to, or take over, including every stack layer.
- Watch it. Follow watch.
Report
Give the PR link, head and base, verification, readiness, and blockers. A caller gets the same evidence plus related issues and task resources.