code-reviewer

Analyze JavaScript, Python, Java, Go, and Rust codebases for quality and security issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates comprehensive code reviews, identifying issues across code quality, security, performance, and adherence to best practices, ensuring higher-quality and more robust software.

Core Features & Use Cases

  • Automated Analysis: Performs in-depth checks for SOLID principles, security vulnerabilities (OWASP), performance bottlenecks, and code smells.
  • Structured Feedback: Provides detailed, actionable feedback in Japanese, including severity ratings and specific code examples for improvement.
  • Use Case: Integrate this Skill into your CI/CD pipeline to automatically flag potential bugs, security risks, and performance issues before code is merged, saving developer time and reducing production errors.

Quick Start

Initiate a code review for the files located in the 'src/utils' directory.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I automate code review for SOLID principles and OWASP security vulnerabilities?

Automated code review for SOLID principles and OWASP security vulnerabilities is performed by analyzing your codebase for code smells, security risks, and performance bottlenecks. It provides structured feedback with severity ratings and refactoring suggestions.

Can I get refactoring suggestions for JavaScript, Python, Java, Go, and Rust codebases?

Refactoring suggestions for JavaScript, Python, Java, Go, and Rust codebases are supported through comprehensive static analysis. It identifies performance bottlenecks and SOLID principle violations, providing actionable feedback in Japanese.

What's the best way to integrate static analysis into a CI/CD pipeline to flag bugs before merging?

Integrating static analysis into a CI/CD pipeline to flag bugs before merging is achieved by running automated checks against directories like 'src/utils'. It automatically identifies security risks and code smells before code is merged.

Does this code review tool support analysis for code smells and performance bottlenecks?

Code review analysis for code smells and performance bottlenecks is fully supported using ComplexityAnalyzer. It checks for SOLID principles and OWASP vulnerabilities, delivering detailed improvement examples.

Why does the code review feedback require strict documentation language policies?

Code review feedback requires strict documentation language policies to ensure structured outputs consistently use Japanese. This approach maintains standardized, detailed feedback with severity ratings across multiple programming languages.