review-agent

Automate security and performance checks for code changes by applying a code review capability to the PR diff and related tests. This generates a structured findings report with severity ratings and explicit remediation steps suitable for pre-merge validation.

The best way to generate remediation suggestions for pattern compliance deviations is to run a systematic review on changed files and their calling context. This identifies architectural issues and outputs actionable guidance to fix pattern deviations.

Yes, you can use automated code review for ongoing quality improvement outside of a pull request workflow. Simply provide the changed files directly to generate a structured report with severity-rated findings and clear follow-up steps.

Code review for pull requests checks both the changed source code and related test files. Applying the review to changed files alongside their tests ensures correctness validation and produces reproducible verification against established patterns.

Severity rating in automated code review findings reports works by evaluating identified security vulnerabilities, performance bottlenecks, and correctness issues, then structuring them into a clear report with explicit remediation steps based on risk priority.

You need pattern compliance validation for code changes when performing pre-merge gate checks or architectural conformance reviews. It identifies deviations from established patterns and provides clear, reproducible follow-ups to maintain code quality.