techdebt

Scan recent code changes for duplicated logic, dead code, and magic numbers.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/SamyakJhaveri/loam --skill techdebt-samyakjhaveri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: techdebt
Source: https://github.com/SamyakJhaveri/loam/tree/main/seed/.claude/skills/techdebt
Command: npx skills add https://github.com/SamyakJhaveri/loam --skill techdebt-samyakjhaveri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scan codebases for tech debt: duplicated logic, dead code, and magic numbers, to surface improvement opportunities before they become bugs.

Core Features & Use Cases

  • Analyze recently changed files for duplicated logic, dead code, and hard-coded values.
  • Suggest concrete refactors and naming constants to reduce duplication and improve maintainability.
  • Use at end-of-session sweeps to ensure a healthy, debt-free codebase before committing.

Quick Start

Run a quick debt sweep on the current project to surface duplications, dead code, and magic numbers, then review the findings before committing.

Frequently Asked Questions about techdebt

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

FAQPage Schema
How do I find tech debt hotspots in recently changed code?

Run a debt sweep on recently changed files to identify tech debt hotspots by detecting duplicated logic, dead code, and magic numbers. The scan surfaces refactoring opportunities with suggested fixes and guardrails to prevent regressions before final commits.

What is the best way to detect magic numbers and dead code before a commit?

Use an end-of-session static analysis sweep to detect magic numbers and dead code across your project. It analyzes recent changes and presents findings with suggested naming constants and concrete refactors to improve maintainability.

Does this tech debt scanner require external dependencies or components?

No dependencies or components are required to scan for tech debt. The scanner operates independently to analyze your codebase for duplicated logic, dead code, and hard-coded values without needing external packages.

How do I fix duplicated logic and prevent regressions during refactoring?

Review the scanner findings for duplicated logic and apply the suggested concrete refactors. The scanner provides guardrails to avoid regressions, ensuring your codebase remains stable while you reduce duplication and improve code quality.

When should I run a code quality sweep for static analysis?

Apply the static analysis sweep at the end of a coding session before final commits. Running it at this stage ensures you catch newly introduced duplicated logic, dead code, and hard-coded values while the changes are fresh.