pr-review

Review a pull request for production-readiness by inspecting code changes and related docs to identify risks. This process checks production readiness, documentation updates, and test coverage gaps, returning a structured, actionable checklist with concrete file paths and line numbers for any issues found.

To check if a feature branch is ready to merge, run a comprehensive quality review across the submitted patch. This assesses the branch across seven dimensions, including production-readiness, UX, documentation, tests, and safety, to ensure it meets merging standards.

Yes, reviewing a PR diff can return specific file paths and line numbers for identified issues. Instead of high-level approvals, the review produces concrete findings that pinpoint exactly where code quality, test coverage, or documentation gaps exist.

Identify test coverage gaps and documentation updates in a pull request by inspecting the code changes against related docs. The review mechanism explicitly checks for missing test coverage and outdated documentation before producing an actionable checklist.

The PR review process works on submitted patches, full feature branches, and standard pull requests. It applies a seven-dimension checklist approach to assess code quality, safety, and production readiness across any valid set of code changes.