code-review

Identify bugs and edge cases in code diffs with prioritized fixes.

5|Updated Feb 3, 2024
One-click install
npx skills add https://github.com/ahkohd/dotfiles --skill code-review-ahkohd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/ahkohd/dotfiles/tree/main/claude/.claude/skills/code-review
Command: npx skills add https://github.com/ahkohd/dotfiles --skill code-review-ahkohd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides a reviewer to identify bugs, edge cases, state issues, security risks, API contract problems, and testing gaps directly from code diffs.

Core Features & Use Cases

  • Focused diff analysis: Review changes to pinpoint what actually changed.
  • Issue taxonomy: Correctness, State, Performance, Security, API, Test, and more.
  • Prioritized findings: Clear, prioritized format with concrete fixes.
  • Use Case: Before merging a PR, produce a concise, actionable summary of issues and fixes.

Quick Start

  1. Get the diff: git diff or jj diff
  2. Run the review process to generate a structured, prioritized findings report
  3. Review the suggested fixes and apply changes accordingly

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review code diffs to catch bugs before merging?

Code review diffs systematically identifies bugs, edge cases, and security risks in pull request changes. Run a diff analysis to prioritize issues by severity (P0–P3) with concrete fixes and guidance, enabling faster, more thorough PR prechecks before merge.

What issues does a diff-focused code review catch?

Diff review detects correctness errors, state management problems, side effects, error handling gaps, performance issues, security vulnerabilities, API contract violations, and testing gaps. Each finding includes prioritization and suggested fixes for immediate action.

Can I use code review on multiple programming languages?

Yes, diff-based code review applies across languages during PR reviews, post-merge validation, and integration pipelines. It analyzes changes in any language without language-specific setup, focusing on correctness and risk patterns.

How do I get started with a code review process?

Generate a diff using git diff or jj diff, run the review analysis to produce a prioritized findings report with issue taxonomy and concrete fixes, then review and apply suggested changes before merging.

What's the difference between diff review and automated linting?

Diff review prioritizes bugs, logic errors, and security risks specific to changed code with manual guidance; linting checks style and syntax. Together they cover functional correctness and code quality across review pipelines.

Does code review work in CI/CD pipelines?

Yes, diff review integrates into PR precheck and post-merge validation workflows. The structured, prioritized output fits review pipelines, enabling automated issue detection before merge gates or deployment stages.