watch

Watch the MR Until the Review Is Settled

Run a full code review of the current branch's merge request, post it, hand the work back to the author, and then watch it through the watcher agent until every blocking finding and every suggestion has been addressed in code or refuted with a reply.

The handshake invariant. The ticket carries the ball, as teamwork:review-handshake defines it; Phase 0.4 loads that skill.

That is what paces this command. After posting a round of findings, hand the work back per teamwork:review-handshake; the next round runs only when the handshake reads ready-for-review again. This keeps the review out of work-in-progress instead of commenting on every half-finished push.

review → post → hand back (teamwork:review-handshake) → [wait]
   → the author hands over again
   → sync the local branch onto the author's new head
   → revisit every open thread, reply, resolve what is settled
   → review the delta, post new findings
   → anything still open? hand back, wait again
   → nothing open? leave it handed over and stop

This command is the reviewer side of an MR. It is the mirror image of /sdlc:mr-babysit, which is the author side. The distinction matters and is enforced below: this command never edits, commits, pushes, or rebases locally.

$ARGUMENTS

Stance — you are the reviewer, not the author

For the whole lifetime of this command, including every follow-up round:

• Never change the code. No Edit, no Write into the repo, no git commit, no git push, no local git rebase, no git checkout of a different branch, no stash. If a finding has an obvious fix, describe it in the comment. Do not apply it.
• Never resolve a thread the author opened, and never promise anything on the MR — teamwork:review-handshake.

Exactly two kinds of write to git are authorized (the MR draft flag and the ticket status are metadata, not code — see the autonomy grant below):

1. The server-side rebase via glab mr rebase — Phase 1, once, never repeated.
2. The guarded git reset --hard of the local sync procedure — after that rebase, and again at the start of every follow-up round. It fast-forwards the checkout onto the author's current head so re-reviews read fresh code. It never runs over a dirty tree or over local-only commits.