pr-review-agent

To assess pull request merge readiness, you can run a review agent that fetches PR comments via GitHub CLI, scores blast radius on each changed file, and flags high-risk areas before merging. It generates a unified report summarizing triage, scoring, and drift checks.

Architecture drift detection identifies violations introduced by a pull request by running a drift scan since the base SHA. It validates architectural compliance and reports any breaks, ensuring the PR does not compromise existing system structure before merging.

Yes, fetching pull request review comments requires the GitHub CLI. The review agent then categorizes these comments by impact level—security, breaking, logic, performance, naming, and style—to triage and prioritize developer action efficiently.

Yes, code fixes are applied through a triage-fix workflow that waits for explicit developer approval, such as an instruction to fix specific items or all items. It then applies fixes in prioritized order with one commit per fix item.

The best way to prevent risky merges is to combine structured comment triage with objective repository impact checks. This approach evaluates blast radius, detects architecture drift, and scores risk on changed files to block high-risk merges.

You should not use automated pull request review when you need immediate, unprompted code fixes, as the triage-fix workflow requires explicit developer approval for each item. It is designed for structured evaluation rather than autonomous, unsupervised merging.