skills.rest
jankneumann
jankneumannCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

tech-debt-analysis

Analyze codebase complexity, coupling, duplication, and import issues to generate markdown and JSON reports.

4|1|Updated Jan 16, 2026
Search Tags:#refactoring#complexity#duplication#code-analysis#coupling#tech-debt
One-click install
npx skills add https://github.com/jankneumann/agentic-coding-tools --skill tech-debt-analysis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt-analysis
Source: https://github.com/jankneumann/agentic-coding-tools/tree/main/.agents/skills/tech-debt-analysis
Command: npx skills add https://github.com/jankneumann/agentic-coding-tools --skill tech-debt-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Development speed stalls when hidden technical debt accumulates in the codebase. This Skill scans the repository, identifies complexity, coupling, duplication, and import issues, and surfaces the most impactful problems so teams can plan refactoring.

Core Features & Use Cases

  • Complexity Analyzer: Detects long methods, large files, high cyclomatic complexity, deep nesting, and long parameter lists.
  • Coupling Analyzer: Highlights modules with excessive fan‑in/fan‑out and high‑impact nodes using architecture graph artifacts.
  • Duplication Analyzer: Finds cross‑file and same‑file copy‑pasted code blocks.
  • Import Analyzer: Flags circular imports, import fan‑out, and star imports.
  • Use Case: Run the Skill before a sprint planning session to create a prioritized refactoring backlog and improve design stamina.

Quick Start

Run the tech‑debt analysis skill on your project directory to generate a detailed debt report.

Frequently Asked Questions about tech-debt-analysis

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

FAQPage Schema
How do I identify technical debt in a codebase before sprint planning?▼

To identify technical debt in a codebase, analyze structural complexity, coupling, duplication, and import issues. This generates markdown and JSON reports with severity rankings to help prioritize refactoring tasks without altering source files.

What is cyclomatic complexity and how is it measured during code analysis?▼

Cyclomatic complexity during code analysis measures the number of independent execution paths in a method. High cyclomatic complexity, deep nesting, long methods, and large files are detected to pinpoint areas needing refactoring.

How do I find circular imports and reduce module coupling?▼

To find circular imports and reduce module coupling, analyze import fan-out, star imports, and excessive fan-in/fan-out. This highlights high-impact architecture graph nodes and flags problematic dependencies to guide structural refactoring.

What is the best way to detect code duplication across files?▼

The best way to detect code duplication across files is to scan for cross-file and same-file copy-pasted code blocks. A duplication analyzer identifies exact structural matches to consolidate redundant logic during refactoring.

Can I generate a refactoring backlog without modifying my source code?▼

Yes, you can generate a prioritized refactoring backlog without modifying source code. The analysis runs read-only scans of complexity and coupling issues, outputting markdown and JSON reports with recommendations rather than applying changes.

Related Skills

Explore More Software Engineering Skills→
Git-on-my-levelGit-on-my-level
863

desloppify

Scan codebases for health risks and generate prioritized cleanup plans.

Community
Advanced
OmniNode-aiOmniNode-ai
3

insights-to-plan

Parse Claude Code insights HTML reports into prioritized design plans with acceptance criteria.

Official
Advanced
quangphu1912quangphu1912
1

tracing-dependencies

Detects circular dependencies, architectural violations, and conflicts in module graphs via static code analysis.

Community
Advanced
rpelizzarpelizza

pelizzai-improving-architecture

Analyze codebase evidence to identify architectural debt and structural friction.

Community
Advanced