review-pr

Automate GitHub pull request reviews by retrieving PR metadata, inspecting all changed files, and aggregating findings into severity-based feedback with file and line references. The review evaluates code quality, correctness, and implementation risk across engine, UI, and application workflows during branch-based development.

The best way to review code quality and implementation risk before a release is to run a structured validation workflow that pulls branch details and changed files. This process routes engine and UI changes to specialized focus areas, runs build checks, and generates a severity-ranked summary.

Build validation integrates into the GitHub code review workflow by running a build check as part of the inspection process. The build check results are combined with multi-file code analysis to produce an organized review summary suitable for approving, requesting changes, or escalating concerns.

Yes, you can use this automated code review for branch-based development across different application layers. It supports multi-file changes by routing engine changes and UI or app shell changes to the most relevant reviewer focus areas to evaluate correctness and maintainability.

To get a severity-ranked summary with file and line references, provide the pull request number to the review workflow. It retrieves the PR metadata, inspects changed files, runs build validation, and aggregates the findings into an organized feedback report.

No, this GitHub PR review process does not require any external dependencies or components to function. It independently retrieves pull request metadata, performs full changed-file inspection, and aggregates severity-based feedback with file and line references.