code-review-en

Analyze codebases for quality issues and generate severity-categorized reports.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/ousiass/claude-config --skill code-review-en
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-en
Source: https://github.com/ousiass/claude-config/tree/main/skills/code-review-en
Command: npx skills add https://github.com/ousiass/claude-config --skill code-review-en

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the comprehensive review of codebase quality, identifies potential refactoring opportunities, and ensures adherence to coding standards, thereby improving maintainability and reducing technical debt.

Core Features & Use Cases

  • Full Codebase Analysis: Scans the entire project or specified directories/files for quality issues.
  • Multi-faceted Checks: Incorporates checks for common issues, linter rules, frontend-specific patterns (including Atomic Design), backend best practices, and refactoring candidates.
  • Structured Reporting: Generates detailed reports with severity levels, file paths, line numbers, and concrete improvement suggestions.
  • Use Case: Before merging a significant feature branch, run this Skill to get a detailed report on code quality, identify any architectural violations, and ensure the code is ready for production.

Quick Start

Run a full code review on the current project.

Frequently Asked Questions about code-review-en

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

FAQPage Schema
How do I automate code review for my entire codebase before merging a feature branch?

You can automate code review by scanning the entire codebase or specified directories to identify quality issues and refactoring opportunities. This Skill applies predefined check criteria and generates detailed reports for GitHub Issues or local Markdown files.

What is codebase refactoring analysis and how does it identify technical debt?

Codebase refactoring analysis identifies potential refactoring candidates and architectural violations by applying backend and frontend best practices. It categorizes findings by severity with file paths and line numbers to reduce technical debt and improve maintainability.

Does this code analysis tool support frontend architectural patterns like Atomic Design?

Yes, this code analysis tool supports frontend-specific patterns including Atomic Design. It incorporates multi-faceted checks for frontend components alongside backend best practices and common linter rules to ensure adherence to coding standards.

Can I generate code quality reports as GitHub Issues for my development workflow?

Yes, you can generate code quality reports as GitHub Issues or local Markdown files. The structured reporting includes severity levels, file paths, line numbers, and concrete improvement suggestions for your development workflow.

What are the limitations of automated linter checks for identifying refactoring candidates?

While automated linter checks identify common issues and rule violations, complex refactoring candidates require analyzing project structure and applying backend or frontend best practices, categorizing findings by severity to highlight architectural violations.