skills.rest
CANTAGESTUDIO
CANTAGESTUDIOCOMMUNITY
Explore all skills by this author →
GitHub

refactor-scan-tech-debt

Identify code smells, complexity hotspots, duplications, and outdated patterns via static analysis.

3|Updated Dec 22, 2025
Search Tags:#complexity#tech debt#code smells#duplication#outdated-patterns
One-click install
npx skills add https://github.com/CANTAGESTUDIO/CosmicAtlasPacker --skill refactor-scan-tech-debt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: refactor-scan-tech-debt
Source: https://github.com/CANTAGESTUDIO/CosmicAtlasPacker/tree/main/.claude/skills/refactor-scan-tech-debt
Command: npx skills add https://github.com/CANTAGESTUDIO/CosmicAtlasPacker --skill refactor-scan-tech-debt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically surfaces code smells, complexity hotspots, duplications, and outdated patterns to target for refactors.

Core Features & Use Cases

  • Scan Categories: Code smells, complexity indicators, duplication, outdated patterns.
  • Output: Clear list of debt hotspots to prioritize work.

Quick Start

Run a tech debt scan at the start of a refactor to identify focus areas.

Frequently Asked Questions about refactor-scan-tech-debt

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

FAQPage Schema
How do I identify code smells and complexity hotspots in my codebase?▼

Technical debt scanning detects code smells like long methods (>50 lines), large classes (>500 lines), high cyclomatic complexity (>10), and deep nesting (>3 levels) through static analysis. Run a scan to surface complexity hotspots prioritized for refactoring.

What types of technical debt does a static analysis scan catch?▼

Static analysis identifies long methods, large classes, long parameter lists (>4), feature envy, data clumps, deep nesting, cyclomatic complexity violations, god objects, circular dependencies, duplicated code, deprecated APIs, legacy patterns, and dead code.

When should I scan for technical debt during a refactor?▼

Scan for technical debt at the start of refactoring to identify and prioritize code smells and complexity hotspots before planning targeted improvements. Results guide which areas deliver the most impact.

Can I detect duplicated code and outdated patterns automatically?▼

Yes, automated scanning detects duplicated code sections, deprecated APIs, and legacy patterns alongside complexity indicators. This surfaces refactoring opportunities without manual code review.

What's the difference between code smells and complexity metrics?▼

Code smells are structural issues like feature envy or god objects; complexity metrics measure cyclomatic complexity and nesting depth. Both indicate where refactoring effort is needed, often in the same hotspots.

Related Skills

Explore More Software Engineering Skills→
kfolkeskfolkes
2

graudit-security-scan

Scan source code for vulnerability patterns using graudit.

Community
Intermediate
lushly-devlushly-dev
4

refactor-code

Guide systematic code refactoring with extract, inline, move, and rename patterns.

Official
Advanced
Jaydpatel01Jaydpatel01

code-quality-and-review

Enforce code correctness, readability, and safety with linters and type checkers.

Community
Advanced
thktthkt
11

audit

Orchestrate AI agents to audit code quality with tiered review and static analysis.

Community
Advanced