code-reviewer

To review a large git diff, you can use a structured workflow that collapses mechanical changes and guides you to high-risk files and entrypoints. This approach focuses reviewer effort on behavioral deltas to reduce missed regressions.

An actionable pull request review report should include a concise summary, major blockers, heuristic risk hits, proposed fixes, a test plan, and follow-ups. It prioritizes checks for correctness, safety, maintainability, and performance.

Yes, you can generate a structured code review for both frontend and backend pull requests. The review process applies across backend, frontend, and infrastructure code to assess correctness, security, and maintainability.

The best way to automate pull request triage is to apply a repeatable check order that assesses safety, performance, and maintainability. This surfaces heuristic risks and generates a templated markdown review report with changed files.

No external dependencies are required. The workflow uses included scripts and references to render a templated markdown review report, allowing you to assess diffs and propose fixes without additional environment setup.