CodeReview

Diagnose code with Clean Code principles and file:line citations.

1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/mec07/claude_skills --skill codereview-mec07
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: CodeReview
Source: https://github.com/mec07/claude_skills/tree/main/stow/CodeReview
Command: npx skills add https://github.com/mec07/claude_skills --skill codereview-mec07

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide structured, opinionated code reviews based on Clean Code principles to identify architectural concerns, maintainability gaps, and plan-alignment issues without rubber-stamping.

Core Features & Use Cases

  • Six review lenses (Architecture & Responsibility, Type Safety & Contracts, State Management, Testing, Pragmatics & Maintainability, Production Readiness) to guide thorough assessments.
  • Plan-alignment reviews that compare implemented changes against original plans or specifications using git diff ranges.
  • Dual workflows: Full Codebase Review for broad assessment and Single File Deep Dive for focused feedback, with citations and actionable recommendations.
  • Generates results with file:line citations and severity tiers to help teams prioritize fixes and maintain quality.

Quick Start

Request a full CodeReview on the latest changes or a single-file review by specifying the target path.

Frequently Asked Questions about CodeReview

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

FAQPage Schema
How do I perform a code review based on Clean Code principles?▼

Code review based on Clean Code principles diagnoses and critiques code using a structured, opinionated review across six lenses, returning findings with file:line citations, severity tiers, and concrete recommendations to improve architecture and maintainability.

What is the best way to check if my code changes align with the original architecture plan?▼

Plan-alignment reviews compare implemented changes against original specifications using git diff ranges, identifying architectural concerns and maintainability gaps without rubber-stamping to ensure the codebase matches the original design intent.

Can I run a focused code quality check on a single file instead of the whole codebase?▼

Single File Deep Dive workflows provide focused feedback on individual files, applying the same six review lenses, file:line citations, and severity tiers to assess type safety, state management, and production readiness.

How does an Uncle Bob style code review assess production readiness?▼

Uncle Bob style code reviews apply Clean Code principles through six lenses including Production Readiness, evaluating type safety, state management, and pragmatics to return severity-tiered findings with concrete recommendations.

What are the six lenses used for structured codebase reviews?▼

Structured codebase reviews evaluate code across six lenses: Architecture & Responsibility, Type Safety & Contracts, State Management, Testing, Pragmatics & Maintainability, and Production Readiness, ensuring thorough maintainability and quality assessments.

Does this code review approach work across different programming languages and projects?▼

Yes, this structured code review applies Clean Code principles across languages and projects, guiding architecture checks and maintainability assessments for both full codebases and individual files with actionable file:line citations.