code-reviewer

Detect code smells and quality issues in git diffs, files, or projects.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/physics91/claude-vibe --skill code-reviewer-physics91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/physics91/claude-vibe/tree/main/skills/code-reviewer
Command: npx skills add https://github.com/physics91/claude-vibe --skill code-reviewer-physics91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes code quality, detects code smells, and suggests improvements to accelerate reviews and reduce defect risk.

Core Features & Use Cases

  • Automated Quality Checks: Run static analysis, style checks, and bug detection to surface issues early.
  • Code Smell Detection: Identify issues like long functions, deep nesting, and magic numbers.
  • Refactoring Suggestions: Propose concrete improvements to improve readability and maintainability.
  • Use Case: Before merging a PR, generate a prioritized list of improvements and suggested patches.

Quick Start

To review a code changeset, invoke the Code Reviewer on your target path using the /analyze-code command, e.g., /analyze-code path/to/target.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I detect code smells and quality issues in my project?

Code smell detection identifies structural problems like long functions, deep nesting, and magic numbers that harm maintainability. Run the /analyze-code command on your target path to surface these issues with severity ratings and refactoring suggestions.

Can I use code review automation on git diffs and pull requests?

Yes. Static analysis and code quality checks run on git diffs, specific files, folders, full project scans, or recent commits during PR reviews. The Skill generates prioritized improvement lists and copy-paste-ready remediation steps for targeted fixes.

What code quality metrics does the analysis measure?

Analysis measures cyclomatic complexity, cognitive complexity, code duplication, naming quality, function length, and nesting depth. These metrics combine with style checks and bug detection to provide severity-based fix suggestions.

How do I speed up code reviews with automated analysis?

Invoke /analyze-code on your changeset before merging to run linting, refactoring suggestions, and static analysis automatically. This surfaces defects early and reduces manual review time by prioritizing issues by severity.

Does code review automation work with existing refactoring workflows?

Yes. The Skill integrates into code review pipelines by detecting refactoring opportunities, suggesting concrete improvements, and providing copy-paste-ready remediation steps alongside complexity and duplication metrics.