review-code

Code review for your git diff is automated by analyzing active branch changes against a base branch. The Skill reads modified files and adjacent modules to summarize intent and classify issues by severity, providing specific improvement suggestions.

The best way to perform diff analysis for bug detection is using a Principal Software Engineer perspective. This approach evaluates changed logic intent and impact scope to identify bugs, security vulnerabilities, and performance bottlenecks within the git diff.

You review only the current changes on your active branch, not unrelated commits. The Skill targets the specific diff output, such as from git diff HEAD, ensuring the code review remains focused on your latest modifications.

Identified issues are classified into categories such as BUG, ISSUE, and improvement opportunities. The Skill categorizes code quality problems by defined severity levels and provides specific improvement suggestions based on the analyzed diff.

Yes, this code review approach reads related files outside the direct diff. It inspects imported files and structurally adjacent modules to understand the full context and evaluate the true impact scope of the modified logic before classifying issues.