tech-debt-check

Identify technical debt patterns in codebases using duplication, complexity, and file-size metrics.

2|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/benjaminshoemaker/benshoemaker-us --skill tech-debt-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt-check
Source: https://github.com/benjaminshoemaker/benshoemaker-us/tree/main/.claude/skills/tech-debt-check
Command: npx skills add https://github.com/benjaminshoemaker/benshoemaker-us --skill tech-debt-check

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Identify technical debt patterns in codebases to improve maintainability.

## Core Features & Use Cases

  • Duplication detection: Find repeated code blocks across the project.
  • Complexity analysis: Measure average and max cyclomatic complexity.
  • File size and structure checks: Flag oversized files and long methods.
  • Use Case: Run at phase checkpoints during AI-assisted development to surface debt before it compounds.

### Quick Start Use the tech-debt-check skill to scan a project and generate a high-level report on debt hotspots.

Frequently Asked Questions about tech-debt-check

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

FAQPage Schema
How do I identify technical debt patterns in my codebase?

You can measure technical debt by analyzing cyclomatic complexity, detecting code duplication, and flagging oversized files to surface debt hotspots before they compound during development.

What is the best way to track code complexity and duplication during development?

Run static analysis at phase checkpoints to measure average and max cyclomatic complexity, detect repeated code blocks, and flag long methods to prevent technical debt from compounding.

How do I generate a prioritized remediation plan for static analysis findings?

Apply a structured analysis workflow with defined complexity and file-size thresholds, incorporate optional AI code-smell checks, and output a prioritized remediation plan targeting the highest debt hotspots.

Can I use static analysis to find duplicated code blocks across a project?

Yes, static analysis can detect repeated code blocks across a project by scanning the codebase for duplication patterns and flagging them in a technical debt report to improve maintainability.

When should I run a technical debt assessment on my codebase?

Run technical debt assessments at phase checkpoints during AI-assisted development to surface debt before it compounds, or on-demand to evaluate duplication, complexity, and file-size metrics.

Does technical debt analysis work without setting complexity thresholds?

No, a structured analysis workflow requires defined thresholds to evaluate complexity and file-size metrics, ensuring the technical debt report generates a meaningful prioritized remediation plan.