pr-review

To review a pull request for security and backward compatibility, analyze the code diff for vulnerabilities and breaking changes. This process evaluates code quality, test coverage, and design decisions that CI cannot automatically verify, providing concrete file-level remediation recommendations.

Checking code quality beyond CI involves evaluating design decisions, test coverage, and security vulnerabilities. This review process produces structured, file-level observations and concrete remediation recommendations for issues that automated CI pipelines miss.

You can review local branch diffs directly without needing a GitHub PR URL. The review process is context-aware and works with GitHub PRs, local branches, or code diffs, producing structured observations and recommendations based on the provided input.

To get actionable feedback on test coverage during a code review, evaluate the pull request focusing on test coverage gaps. This produces precise file paths and concrete remediation recommendations to enhance tests alongside security and backward compatibility checks.

Yes, this pull request review process works with local code diffs. It applies context-aware analysis to GitHub PRs, local branches, or raw diffs to evaluate code quality, design decisions, test coverage, security, and backward compatibility.

Automated code reviews focus on limitations of CI by checking design decisions, security vulnerabilities, and backward compatibility. However, they require a provided PR number, URL, or diff to generate structured, file-level observations and concrete remediation recommendations.