resolve-pr-comments-stack

Run gt log --stack to establish dependency order, then check out each branch bottom-up, fetch unresolved review threads via the GitHub GraphQL API, and triage each as FIX, REPLY, or SKIP. Commit each branch's fixes with gt modify -a so descendants restack automatically.

The single-PR resolve-pr-comments skill handles one standalone PR's triage loop. The stack version adds ordering, per-branch persistence via gt modify, and cross-branch judgment, invoking the same per-PR triage logic once per branch internally.

Publishing is strictly the user's action with no approval that transfers it. The pass ends with work committed locally via gt modify; the user runs gt submit --stack themselves, then remote heads are verified against local tips before re-checking threads.

No. Bot threads auto-resolve once the fixed branch is pushed, so silence plus the push is the signal. Only human-reviewer threads get an explanatory reply describing what changed, and never the bare word Fixed.

The loop stops on the conflicted branch and a gated recovery begins: show the user the conflicted files and intended resolutions, hand-resolve each region, verify no conflict markers remain, then gt add and gt continue. Nothing is edited without explicit approval.

Yes. Every approved FIX runs red-green TDD, including comment and documentation findings where the underlying claim is asserted in a test. The only exception is code that genuinely cannot be exercised locally, which must be flagged in the final summary.