techdebt

Scan TypeScript/JavaScript codebases for duplicates, unused imports, and debug code.

125|35|Updated Jan 21, 2026

Search Tags:#typescript #refactor #code-quality #tech debt #grep #static-analysis

Ready to run

npx skills add https://github.com/jh941213/my-claude-code-asset --skill techdebt-jh941213

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: techdebt
Source: https://github.com/jh941213/my-claude-code-asset/tree/main/skills/techdebt
Command: npx skills add https://github.com/jh941213/my-claude-code-asset --skill techdebt-jh941213

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintainers identify and remediate technical debt in a codebase by surfacing duplicated logic, unused imports, and debugging artifacts before they become costly issues.

Core Features & Use Cases

Duplicate code detection: spot repeated logic across files and flag candidates for refactoring.
Unused and debugging code discovery: find unused imports, dead variables, console.log/debugger statements.
Code quality guidance: provide a concise remediation report that highlights actionable fixes and refactor opportunities.
Use Case: Imagine a large TypeScript project with shrinking maintainability; run this Skill to generate a debt report and prioritize cleanup tasks before release.

Quick Start

Run a tech debt scan on your repository to identify and report duplicates, unused imports, and debug statements. Then review and apply fixes, re-running the scan to verify improvements.

Frequently Asked Questions about techdebt

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

FAQPage Schema

How do I find technical debt in a TypeScript codebase?▼

You can detect technical debt in a TypeScript project by scanning for duplicate code, unused imports, console logs, and overly long functions. This produces a structured report highlighting actionable fixes and refactor opportunities.

What is the best way to detect unused imports and debug statements in JavaScript projects?▼

The best way to detect unused imports and debug statements is to run an automated static analysis scan across your JavaScript project. This surfaces dead variables, console logs, and debugger artifacts before they become costly maintenance issues.

Does this technical debt scanner require any external dependencies or components?▼

No external dependencies or components are required. You can run the technical debt scan directly on your TypeScript or JavaScript codebase to identify duplicated logic, unused imports, and debugging artifacts without installing additional modules.

How do I identify duplicate code for refactoring in a large TypeScript project?▼

To identify duplicate code for refactoring, scan the codebase to spot repeated logic across files. The scan flags candidates for refactoring and provides a concise remediation report to prioritize cleanup tasks before release.

When do I need to scan for code quality issues and technical debt?▼

You need to scan for code quality issues and technical debt when a large TypeScript project experiences shrinking maintainability. Running a scan before release generates a debt report to identify duplicates, unused imports, and debug statements.