What problem does it solve? Reviewers leave inline comments on a pull request and the author must work through each one: decide whether to change code, make the fix, commit it, and write a reply per thread. Doing this manually is slow and threads get missed, leaving reviewers unsure whether their feedback was seen. ## Core Features & Use Cases - Thread-by-thread triage: Reads every unresolved review thread via the GitHub API, classifies each as fix, decline-with-reason, or ask, and acts on each one individually. - Generated-code awareness: Uses a change review to distinguish fully generated files (fixed by changing the model and rerunning the software factory) from hand-written files (edited directly), so fixes survive regeneration. - One commit per thread with staged replies: Commits each fix separately and stages all replies into the user's pending review in a single call, never pushing or submitting on the user's behalf. - Use Case: A pull request on an Intent Architect solution returns with eight unresolved comments, some on generated code. The skill fixes model-level issues through the designer, patches custom code directly, runs the build, commits each fix, and stages a reply per thread for the user to review and submit. ## Quick Start Ask the assistant to address the unresolved review comments on pull request 42 in this repository, working from the worktree cut at its head commit.
