Code Review Skill

Run linting and tests, analyze diffs, and generate structured code review reports.

Updated Nov 17, 2025
One-click install
npx skills add https://github.com/grumps/claude-dotfiles --skill code-review-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Code Review Skill
Source: https://github.com/grumps/claude-dotfiles/tree/main/skills/reviewing
Command: npx skills add https://github.com/grumps/claude-dotfiles --skill code-review-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual code reviews can be time-consuming, inconsistent, and prone to human error. This skill automates the initial stages of code review, providing immediate, structured feedback on correctness, style, testing, and security, allowing human reviewers to focus on higher-level architectural concerns.

Core Features & Use Cases

  • Automated Pre-Review Checks: Automatically runs linters (just lint-for-claude) and tests (just test-for-claude) to catch common issues before human review.
  • Comprehensive Review Checklist: Evaluates code against a detailed checklist covering correctness, quality, testing, performance, security, and maintainability.
  • Structured Feedback: Generates a clear, actionable review report with critical issues, suggestions, positive notes, and action items, including file and line references.
  • Use Case: Before submitting a pull request, use /review-code. The skill will run all checks, analyze your changes, and provide a detailed report, helping you catch and fix issues proactively, leading to faster approvals and higher quality code.

Quick Start

Ask Claude to "Review my staged code changes and provide feedback."

Frequently Asked Questions about Code Review Skill

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

FAQPage Schema
How do I automate code reviews before submitting pull requests?

Automated code reviews analyze your changes against a comprehensive checklist covering correctness, style, testing, performance, security, and maintainability. Use `/review-code` or ask Claude to review your staged changes; the skill runs linters and tests automatically, then generates a structured report with critical issues, suggestions, and actionable feedback to catch problems before human review.

What does a code review checklist typically cover?

A code review checklist evaluates correctness, code quality, testing coverage, performance implications, security vulnerabilities, maintainability standards, and language-specific conventions. For Go, Python, and Kubernetes manifests, the skill applies relevant best practices and standards to ensure comprehensive feedback across all dimensions.

Can I use automated code review with linting and testing together?

Yes. Automated code review runs linting and tests as part of the initial review stage, catching common issues before the comprehensive checklist analysis. This combined approach ensures both automated checks and structured evaluation of correctness, quality, and adherence to standards happen in a single workflow.

How does automated code review reduce review time for human reviewers?

By automating linting, testing, and generating a detailed review report with file and line references, automated code review eliminates repetitive checks and surfaces critical issues upfront. Human reviewers can then focus on higher-level architectural concerns, design decisions, and logic validation instead of catching style violations or obvious bugs.

What programming languages and formats does code review support?

Code review includes language-specific standards for Go and Python, plus support for Kubernetes manifests. It evaluates these against domain-appropriate best practices for correctness, style, testing, performance, security, and maintainability.

What's the difference between manual and automated code review?

Manual code review relies on human judgment and is prone to inconsistency and fatigue. Automated code review provides immediate, structured feedback using linters, tests, and a comprehensive checklist, reducing time and human error while ensuring consistent standards are applied to every change.