skills.rest
aroido
aroidoOFFICIAL
Explore all skills by this author →
WebsiteGitHub

code-smell-detection

Detect and analyze code smells across components, hooks, types, and architecture.

Updated Apr 22, 2026
Search Tags:#code quality#refactoring#technical debt#software architecture#code smell#sqale
One-click install
npx skills add https://github.com/aroido/vibesmith --skill code-smell-detection-aroido
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-smell-detection
Source: https://github.com/aroido/vibesmith/tree/main/.cursor/skills/code-smell-detection
Command: npx skills add https://github.com/aroido/vibesmith --skill code-smell-detection-aroido

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies and quantifies code smells, providing a clear assessment of technical debt and prioritizing refactoring efforts to improve code quality and maintainability.

Core Features & Use Cases

  • Detects various code smells: Identifies issues in components, hooks, types, and architecture.
  • Assesses technical debt: Calculates a debt score based on the severity and estimated fix time for each smell.
  • Prioritizes refactoring: Provides a ranked list of issues to address, focusing on critical problems first.
  • Use Case: Improve the health of a large codebase by systematically identifying and addressing code smells, leading to more robust and easier-to-maintain software.

Quick Start

Analyze the current project for code smells and provide a refactoring priority list.

Frequently Asked Questions about code-smell-detection

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

FAQPage Schema
How do I detect code smells in my software architecture to reduce technical debt?▼

Detect code smells by evaluating components, hooks, types, and architecture using the SQALE methodology, which assesses technical debt by calculating severity and estimated fix time to prioritize refactoring efforts for your software.

What is the best way to prioritize refactoring efforts in a large codebase?▼

The best way to prioritize refactoring is to generate a ranked list of code smells sorted by a technical debt score, which is calculated using the severity of each issue and its estimated fix time, allowing you to focus on critical problems first.

How does SQALE methodology assess technical debt in software engineering?▼

SQALE methodology assesses technical debt by identifying code smells across components, hooks, types, and architecture, then estimating fix time and severity to calculate a quantifiable debt score for prioritizing software maintenance.

Can I use code smell detection for React component and hook architecture?▼

Yes, code smell detection specifically analyzes components and hooks, along with types and overall architecture, to identify structural issues and calculate technical debt for targeted refactoring in your codebase.

When do I need to run a code smell analysis on my project?▼

You need to run a code smell analysis when maintaining a large codebase and aiming to systematically improve code quality, assess technical debt, and reduce maintenance overhead by identifying architectural and component-level issues before they compound.

Related Skills

Explore More Software Engineering Skills→
clay-goodclay-good
270

spec-gen-generate

Extract OpenSpec specifications from codebases using static analysis and LLM-assisted inference.

Community
Advanced
luispabonluispabon
6

slop-detector

Crawl codebase directories to identify technical debt and code smells.

Community
Advanced
MathiasPaulenkoMathiasPaulenko

sonarqube-quality-gates

Enforce SonarQube quality gates and static analysis in CI/CD pipelines.

Community
Advanced
xlelibertyxleliberty

code-reviewer

Analyze git pull requests for security vulnerabilities and SOLID violations.

Community
Advanced