Collect
Bring GitHub threads and local AI findings into one PR-scoped session.
Built for the last mile of AI-assisted development
gh-address-cr is an open-source GitHub PR review resolution workflow for AI coding agents. Turn review comments and local findings into verified, auditable outcomes—without losing the context behind “done”.
The problem with “done”
Review resolution is not a checkbox. It is a chain of decisions: what changed, why it is safe, which revision was tested, and whether the final state is still true. gh-address-cr keeps that chain attached to the pull request.
One deterministic loop
Bring GitHub threads and local AI findings into one PR-scoped session.
Separate actionable issues, stale context, and findings that need evidence.
Bind proof to the exact commit, files, and command that verified the repair.
Get a fresh, machine-readable completion signal before calling the PR done.
Replies, resolves, validations, and final-gate results remain inspectable and reproducible.
Read the contract ↗Revision and topology changes invalidate stale proof before they can create a misleading green check.
See the workflow ↗A deterministic, local-first CLI keeps ownership clear while Codex, Claude, Copilot, or other agents supply structured evidence.
Get started ↗Fits the way you ship
Keep GitHub conversations useful and make every resolution explainable to the next reviewer.
Let agents focus on reasoning while the runtime owns state, side effects, evidence, and completion semantics.
Refresh evidence when a lower layer changes, so a cascading rebase cannot quietly invalidate your gate.
Start in one command
Use it alongside the coding agent and review producer you already have. The runtime owns state and GitHub side effects; agents return structured evidence.
Read the quickstart ↗$ uv tool install gh-address-crInstall the local runtime first. pipx is also supported ↗
$ npx skills add
github.com/RbBtSn0w/gh-address-cr
--skill skillThen run gh-address-cr agent manifest to verify the installed contract.
Questions, answered
No. It is the resolution and completion layer. Your preferred review producer or coding agent supplies findings; gh-address-cr tracks, validates, replies, resolves, and gates them.
Validation evidence is tied to the current commit and changed files. A new head revision or stacked-PR topology change makes stale proof ineligible until it is refreshed.
No. The local-first CLI and structured agent protocol are designed to work with Codex, Claude, Copilot, and other agents that can return the documented evidence format.
Yes. PR-scoped sessions retain the evidence ledger and final-gate artifacts so the completion decision can be reviewed instead of inferred from a green check alone.
Make “done” mean something