refactor-scan-tech-debt

[Code Quality] Scans codebase for technical debt indicators: code smells, complexity hotspots, duplications, outdated patterns, and anti-patterns. Use when starting a refactoring session to identify what needs attention.

⭐1stars🔀0forks📁View on GitHub🕐Updated Dec 25, 2025

When & Why to Use This Skill

This Claude skill provides a comprehensive automated scan for technical debt, enabling developers to systematically identify code smells, complexity hotspots, and architectural anti-patterns. By analyzing factors like cyclomatic complexity, code duplication, and deprecated legacy patterns, it streamlines the refactoring process and ensures long-term codebase maintainability and performance.

Use Cases

  • Refactoring Preparation: Identify high-complexity 'God Objects' and long methods to prioritize areas for structural improvement before a major refactor.
  • Legacy Code Audit: Detect deprecated APIs and outdated coding patterns when modernizing or migrating older software systems to current standards.
  • Codebase Health Monitoring: Periodically scan for 'code smells' and deep nesting to maintain high standards of readability and prevent the accumulation of technical debt.
  • Architectural Cleanup: Uncover circular dependencies and parallel hierarchies that complicate system architecture and hinder modular testing.
namerefactor-scan-tech-debt
description"[Code Quality] Scans codebase for technical debt indicators: code smells, complexity hotspots, duplications, outdated patterns, and anti-patterns. Use when starting a refactoring session to identify what needs attention."

Refactor: Scan Tech Debt

Identify technical debt across the codebase systematically.

Scan Categories

1. Code Smells

  • Long Methods (> 50 lines)
  • Large Classes (> 500 lines or > 10 public methods)
  • Long Parameter Lists (> 4 parameters)
  • Feature Envy, Data Clumps

2. Complexity Indicators

  • Deep Nesting (> 3 levels)
  • Cyclomatic Complexity (> 10 branches)
  • God Objects
  • Circular Dependencies

3. Duplication

  • Copy-Paste Code
  • Parallel Hierarchies
  • Repeated Conditionals

4. Outdated Patterns

  • Deprecated APIs
  • Legacy Patterns
  • Dead Code