debt-scan

Scan TypeScript/JavaScript codebases for anti-patterns and technical debt.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ItsMattG/property-tracker --skill debt-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debt-scan
Source: https://github.com/ItsMattG/property-tracker/tree/main/.claude/skills/debt-scan
Command: npx skills add https://github.com/ItsMattG/property-tracker --skill debt-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual code-quality reviews are time-consuming and error-prone; debt-scan helps teams quickly identify anti-patterns and technical debt across a codebase.

Core Features & Use Cases

  • Scan the codebase for known anti-patterns from .claude/rules/anti-patterns*.md files and generate counts, locations, and trend comparisons.
  • Produce a consolidated report suitable for code reviews, audits, and prioritizing remediation.
  • Use Case: For a large TS/JS project with a src directory, debt-scan surfaces hotspots and tracks improvement over time.

Quick Start

Run debt-scan against your codebase to generate an anti-patterns and technical debt report.

Frequently Asked Questions about debt-scan

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

FAQPage Schema
How do I identify technical debt and anti-patterns in a TypeScript codebase?

debt-scan identifies technical debt in TypeScript/JavaScript projects by scanning the src directory for known anti-patterns, generating a report with per-pattern counts, file locations, and trend history.

How do I track code quality trends over time in a JavaScript project?

debt-scan tracks code quality trends by comparing anti-pattern counts and locations against previous scans, producing a trend history report for your JavaScript project.

Do I need specific anti-pattern rules to scan my code for technical debt?

Yes, scanning for technical debt requires anti-pattern definitions stored in .claude/rules/anti-patterns*.md files, which the scanner reads to locate and quantify matching code hotspots.

Does debt-scan work with JavaScript files or only TypeScript sources?

debt-scan works with both JavaScript and TypeScript sources, applying to any project containing a src directory to identify and quantify anti-patterns and technical debt.

What is the best way to quantify code anti-patterns for a remediation audit?

The best way to quantify code anti-patterns for an audit is to scan the codebase against defined rules, producing a structured summary with counts and locations to prioritize remediation efforts.

What limitations are there when scanning for technical debt outside a src directory?

Scanning for technical debt is limited to projects with a src directory; sources outside this structure are not included in the anti-pattern counts, file locations, or trend comparisons.