skills.rest
dmitryprg-ai
dmitryprg-aiCOMMUNITY
Explore all skills by this author →
GitHub

techdebt-scan

Detects and fixes TypeScript/JavaScript technical debt via a four-phase SCAN-to-VERIFY workflow.

9|2|Updated Jan 9, 2026
Search Tags:#tdd#refactor#scan#code-smells#codequality#techdebt
One-click install
npx skills add https://github.com/dmitryprg-ai/cursor-develop-autorules --skill techdebt-scan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: techdebt-scan
Source: https://github.com/dmitryprg-ai/cursor-develop-autorules/tree/main/.cursor/skills/techdebt-scan
Command: npx skills add https://github.com/dmitryprg-ai/cursor-develop-autorules --skill techdebt-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Scan codebases to identify and remediate technical debt safely using a test-driven workflow, reducing oversized files, duplicated code, and code smells.

Core Features & Use Cases

  • Scanning & Detection: Locate oversized files, duplicate patterns, long functions, and other code smells.
  • Safe Refactoring with TDD: Apply fixes via a four-phase workflow: SCAN, TEST CASES, REFACTOR, VERIFY, ensuring test coverage.
  • Use Case: Teams aiming to improve code quality in TypeScript/JavaScript projects can run the scanner to surface issues and refactor with confidence.

Quick Start

Run the Phase 1 SCAN to identify issues, then proceed through TEST CASES, REFACTOR, and VERIFY to complete the cleanup.

Frequently Asked Questions about techdebt-scan

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

FAQPage Schema
How do I safely refactor technical debt in a large TypeScript codebase?▼

To safely refactor technical debt in TypeScript, use a test-driven workflow that scans for code smells and oversized files, writes test cases, applies refactoring, and verifies the changes. This ensures your test coverage protects against regressions during the cleanup.

What is the best way to find code smells and duplicated logic in JavaScript projects?▼

The best way to find code smells and duplicated logic in JavaScript projects is to run a scanner that detects oversized files and duplicate patterns. This scanning phase identifies technical debt hotspots so you can prioritize which areas to fix first.

Do I need ripgrep and a local shell environment to scan for technical debt?▼

Yes, you need a local shell environment with ripgrep installed and a working test runner to scan for technical debt. These dependencies are required to execute the scanning, test case generation, refactoring, and verification phases.

Can I use this test-driven refactoring approach on medium-to-large JavaScript projects?▼

Yes, you can use this test-driven refactoring approach on medium-to-large JavaScript projects. It is specifically designed to apply to medium-to-large TypeScript and JavaScript projects that have code smells, duplicated logic, and oversized files.

How does the test-driven workflow fix technical debt without breaking existing functionality?▼

The test-driven workflow fixes technical debt without breaking functionality by following a four-phase process: SCAN to locate issues, TEST CASES to ensure coverage, REFACTOR to apply fixes, and VERIFY to confirm the changes. This sequence guarantees that tests validate every modification.

Related Skills

Explore More Software Engineering Skills→
ortus-boxlangortus-boxlang

commandbox-testing

Run TestBox tests from the CommandBox CLI with configurable reporters.

Official
Intermediate
atstaeffatstaeff
2

project-management

Guide Scrum project setup with CI/CD pipelines and technical debt strategies.

Community
Advanced
vladm3105vladm3105
16

refactor-flow

Detect code smells and plan safe refactoring across multi-repository systems.

Community
Advanced
forgivesam168forgivesam168
2

refactor

Refactor legacy code in small test-driven steps without changing external behavior.

Community
Advanced