github-workflow

Install code-review-core alongside this. On its own there is nothing for this plugin to post. code-review-core runs the review — detectors, judgement agents, then a validator that re-reads every cited line — and writes .code-review/VALIDATED.json. This plugin is the other half: it talks to GitHub, and it forms no opinion about the code. The two communicate through that one file and nothing else.

Beyond the transport it owns the pull request lifecycle over the gh CLI — opening a PR, watching its checks, working through review feedback, merging with the strategy the repository actually permits — and GitHub Actions authoring: workflow anatomy, SHA pinning, permissions, OIDC and debugging.

Prerequisites are gh, authenticated, and jq. Both must be present; the posting script exits non-zero with a clear message rather than degrading, because a transport that half-works posts half a review.

Do not reach for it if you want issues, labels, milestones or project boards — that is github-issues — or if you are on anything that is not GitHub. Nothing here is portable, on purpose: the forge-neutral half already exists in the core, so a second transport can be written without touching the judgement. It also refuses to post a review that was never run, and that refusal is the most important thing it does.