Review threads

Turn a pile of review feedback into one pass: gather -> judge -> fix -> draft -> confirm -> reply and resolve. The skill decides nothing on the user's behalf remotely; everything that lands on the PR passes the gate in step 5.

Two modes, set by the arguments:

• reply mode (default): judge every thread, answer it, resolve what is settled. A comment that deserves a change ends as a fix verdict and a line in the report, the change itself is left to the user.
• fix mode (fix as an argument, or the user asking to fix the comments): the same pass, plus step 3, which writes the changes the fix verdicts call for and commits them.

Boundaries. Nothing leaves the machine before the gate. Local edits and staging happen before it (they are reversible, and the gate needs the diff to be real), commits and the push happen after it. The skill never force-pushes, never rebases, and never touches a branch other than the PR's head.