code-review

You can automate code review for a git branch diff by applying the skill to generate a severity-organized report. It analyzes the provided diff scope and outputs categorized findings with file:line references and targeted remediation suggestions.

Yes, you can check local commits for security and quality issues by applying the review process to your HEAD changes. It identifies issues across languages and produces a structured report categorized as Critical, Warnings, and Suggestions with actionable fixes.

The best way to generate a structured PR review report is to process the PR diff through an automated review. This categorizes findings by severity—Critical, Warnings, and Suggestions—and provides file:line references with prioritized, actionable fix suggestions to present to teammates.

Automated code review works across multiple programming languages when reviewing code changes. It identifies issues in the provided diff scope and produces a severity-organized report with specific file:line references and remediation suggestions regardless of the language used.

To get actionable fix suggestions when reviewing a PR diff, apply an automated review to the changes. The process prioritizes findings and outputs targeted remediation suggestions categorized by severity, helping you address Critical issues and Warnings efficiently.