gitnexus-pr-review

Pull request risk analysis maps code changes to affected execution flows and symbols to quantify blast radius, verify correctness, and identify missing test coverage. It uses GitNexus change detection to evaluate production repository PRs and outputs structured merge recommendations.

Blast radius analysis for a GitHub pull request quantifies the upstream dependency impact of code changes, including potential breakage from direct dependencies. It maps modified symbols to their execution processes to assess the overall risk of merging the PR.

Reviewing a GitHub PR with a dependency graph involves retrieving the diff and mapping the changed code to impacted symbols and processes. This impact analysis evaluates downstream effects and missing test coverage to generate a risk level and merge recommendation.

Yes, PR risk assessment integrates with existing GitHub workflows by using gh-based diff retrieval to fetch pull request changes. It then applies GitNexus change detection tools to map the diff to affected flows and output a structured review.

Automated impact analysis for pull requests should be used when a PR touches core business logic in production repositories. It helps verify correctness, assess blast radius, and determine whether enough tests exist before merging high-risk code changes.