pr-review-sweep

To audit GitHub pull request comments and prevent critical bugs, you can aggregate asynchronous review feedback from inline comments, reviews, and issue discussions into a single actionable triage view. This targets material PRs involving core logic or destructive paths.

To ensure automated merges don't miss human code review feedback, enforce a mandatory post-merge sweep across all pending bot and human findings. This enforces post-merge discipline by aggregating asynchronous review comments before they impact production.

Yes, you need the GitHub CLI and ghapp extension to triage pull request reviews. These dependencies are required to perform authenticated API reads across inline code comments, PR-level review summaries, and issue-level discussions.

The best way to aggregate inline code comments and PR review summaries is to perform an authenticated API sweep across the repository. This identifies and resolves critical logic errors or destructive code paths flagged by bots or humans after a PR is opened.

You should sweep pull request feedback for state-mutating operations when dealing with material PRs involving core source or concurrency. This ensures all bot and human findings are triaged to prevent P1 bugs from slipping through into production.