code-review

Review local and GitHub PR diffs with a severity-based checklist.

Updated Jan 19, 2016
One-click install
npx skills add https://github.com/skinnybrian/dotfiles --skill code-review-skinnybrian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/skinnybrian/dotfiles/tree/main/claude/skills/code-review
Command: npx skills add https://github.com/skinnybrian/dotfiles --skill code-review-skinnybrian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review is time-consuming and error-prone when applied manually to local changes or PRs. This Skill provides a deterministic, phase-driven workflow that guides the user through context gathering, high-level evaluation, and a precise, per-file checklist with severity labeling.

Core Features & Use Cases

  • Phase-based review supports local diffs, PR diffs, staged changes, and deep review modes with a unified, reproducible process.
  • Deterministic guidance via a CLAUDE-style checklist that surfaces issues with clear severity levels and actionable suggestions.
  • PR-ready reporting that can be integrated into development workflows and code review pipelines across local and GitHub contexts.

Quick Start

Run the code-review Skill to analyze the current repository changes and generate a structured review report.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code reviews for local diffs and GitHub PRs?

Automate code reviews by parsing local diffs or GitHub PR changes and applying a severity-based checklist across a multi-phase evaluation. The workflow identifies issues, assigns severity levels, and generates a standardized, actionable review report.

What is a structured code review checklist and how does it work?

A structured code review checklist is a deterministic, phase-driven workflow that evaluates diffs against a formal reference. It works by gathering context, performing high-level evaluation, and applying a per-file checklist with severity labeling to surface issues.

How do I review staged or deep local changes before committing?

Review staged or deep local changes by running the code review process in staged or deep mode. The system parses the diff HEAD, detects the specified mode, collects the changes, and evaluates them against a formal review reference.

Can I integrate automated PR review reporting into my development workflow?

You can integrate automated PR review reporting into development workflows using the standardized output. The process generates PR-ready reports with clear severity levels and actionable suggestions directly from parsed GitHub PR diffs.

Does this code review approach support both local repository changes and GitHub PRs?

This code review approach supports both local repository changes and GitHub PRs. It handles argument parsing and mode detection to seamlessly evaluate local diffs, staged changes, and PR diffs within a unified, reproducible process.

What are the limitations of using a deterministic checklist for code review?

A deterministic checklist for code review limits evaluation to predefined severity-based rules and formal references. It focuses on parsing diffs and applying structured phases, which may not capture nuanced architectural feedback or complex logic flaws outside the checklist scope.