code-review

Automating code review for a pull request involves analyzing code diffs to identify correctness, security, and performance issues. This Skill provides intent-first analysis, reducing false positives by understanding the change's purpose before suggesting actionable fixes.

Intent analysis during diff analysis works by first understanding the purpose behind code changes. This approach focuses the review on relevant issues, ensuring an in-depth understanding without diving into full files unless absolutely necessary for context.

You can categorize code review findings by severity into distinct tiers. This Skill classifies findings into categories like issue, warning, suggestion, nitpick, and praise, helping prioritize actionable fixes and ensure overall code quality.

You need Git installed to analyze code diffs for correctness and security. Git is required for code comparison and diff extraction, enabling the automated review process to detect issues and provide a structured merge verdict.

The best way to review a pull request without manual effort is using an automated, diff-focused analysis tool. This approach evaluates code changes against correctness, security, and performance benchmarks to deliver a merge verdict and actionable suggestions.

You should not use intent-first code review when lacking Git for code comparison, as it is a required dependency. Additionally, if your workflow demands full-file analysis instead of targeted diff evaluation, this approach may not fit your needs.