review-clean-code

Analyze code quality to identify smells and refactoring opportunities.

339|58|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/Heyvhuang/ship-faster --skill review-clean-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-clean-code
Source: https://github.com/Heyvhuang/ship-faster/tree/main/skills/review-clean-code
Command: npx skills add https://github.com/Heyvhuang/ship-faster --skill review-clean-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze code quality to identify smells and refactoring opportunities.

Core Features & Use Cases

  • Automated code-smell detection across naming, function size, duplication, over-engineering, and magic numbers.
  • Severity-guided reports that prioritize issues and provide concrete refactoring suggestions.
  • Use Case: When reviewing a codebase, run this skill to surface high-priority clean-code improvements and generate an actionable refactor plan.

Quick Start

Use the review-clean-code skill to scan your project directory (for example, ./src) and return a prioritized report of issues with suggested fixes.

Frequently Asked Questions about review-clean-code

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

FAQPage Schema
How do I identify code smells and refactoring opportunities in my codebase?

To identify code smells, you can scan your project directory to detect naming issues, function size violations, duplication, over-engineering, and magic numbers. This generates a prioritized report with concrete refactoring suggestions to improve maintainability.

What is the best way to prioritize code quality issues during a code review?

Prioritizing code quality issues is handled through severity-guided reports. The analysis evaluates code smells across multiple dimensions and returns actionable refactoring suggestions ranked by severity, helping you focus on high-priority improvements first.

How do I analyze function size and magic numbers to improve code maintainability?

Analyzing function size and magic numbers involves scanning the codebase for these specific code smells. The process identifies over-engineering and hardcoded values, providing concrete refactoring suggestions to improve overall code maintainability.

Can I use static analysis to generate an actionable refactor plan for a project directory?

Yes, you can use static analysis to scan a specific project directory like ./src. It surfaces clean-code improvements and generates a severity-based report with prioritized, actionable refactoring suggestions for the detected issues.

Does automated code-smell detection work for over-engineering and code duplication issues?

Automated code-smell detection works across naming, function size, duplication, over-engineering, and magic numbers. It identifies these issues in your codebase and provides severity-based recommendations with concrete refactoring suggestions.