dmitryprg-ai/techdebt-scan
.claude/skills/techdebt-scan/SKILL.md
Scan codebase for technical debt including oversized files, duplicated code, code smells, and TODO items. Use when files exceed size limits, when TODO/FIXME/HACK count is growing, when build is slow, when coverage is low, when user says cleanup/tech debt/code quality, or when empty catch blocks or dead code are suspected.
$ install --global
skillsauthnpx skillsauth add dmitryprg-ai/cursor-develop-autorules techdebt-scanInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 2:10 AM5.3s4 files scanned
SKILL.md
- name:
- techdebt-scan
- description:
- Scan codebase for technical debt including oversized files, duplicated code, code smells, and TODO items. Use when files exceed size limits, when TODO/FIXME/HACK count is growing, when build is slow, when coverage is low, when user says cleanup/tech debt/code quality, or when empty catch blocks or dead code are suspected.
- allowed-tools:
- Read, Bash, Grep, Glob
- model:
- sonnet
- user-invocable:
- true
- disable-model-invocation:
- true
Technical Debt Scanner
Find and safely fix technical debt using a TDD approach.
The order SCAN -> TEST CASES -> REFACTOR -> VERIFY exists because fixing debt without tests creates new debt. Skipping the scan leads to fixing low-impact issues while ignoring critical ones.
Phase 1: SCAN
bash ${CLAUDE_SKILL_DIR}/scripts/scan-large-files.sh
bash ${CLAUDE_SKILL_DIR}/scripts/find-todos.sh
Also check for: functions over 50 lines, nesting deeper than 3 levels, files with 10+ exports, magic numbers.
Phase 2: PRIORITIZE
| Impact | Low Effort | High Effort | |--------|-----------|-------------| | High (blocks dev) | P0 — Fix now | P1 — Plan carefully | | Medium (reduces quality) | P2 — Quick win | P3 — Backlog | | Low (cosmetic) | P4 — Optional | Skip |
Phase 3: TEST CASES (before refactoring)
Write tests before changing any code because refactoring without tests is gambling. For each selected issue:
- Create test cases table
- Write failing tests
- Verify tests fail (code not changed yet)
Phase 4: REFACTOR
- Small steps — one file at a time
- Run tests after each change
- Commit after each green test
Phase 5: VERIFY
npm run build— successnpm run lint— 0 errorsnpm test— all passing
What to avoid
- Refactoring without scanning first — you might fix the wrong things
- Skipping test cases — creates new bugs while fixing old debt
- Writing tests after refactoring — defeats the purpose of TDD safety net
- Equating "build passed" with "everything works" — build checks syntax, not behavior
Related Skills
dmitryprg-ai/techdebt-scan
development
VerifiedTrustedCommunity
Scan codebase for technical debt and fix safely with TDD. Use to find oversized files, duplicated code, code smells, and refactor safely. Workflow - SCAN, TEST CASES, REFACTOR, VERIFY. Keywords - techdebt, tech debt, duplicates, code quality audit.
8SKILL.mdUpdated Apr 17, 2026
dmitryprg-ai/tdd-workflow
development
VerifiedTrustedCommunity
Test-Driven Development workflow with strict Red-Green-Refactor cycle. Use when developing features with TDD, writing tests before code, or when test-driven approach is needed. MANDATORY order - test cases table BEFORE code, failing tests BEFORE implementation.
8SKILL.mdUpdated Apr 17, 2026
dmitryprg-ai/session-review
testing
VerifiedTrustedCommunity
Review work session quality and capture improvements. Use at end of session, after large tasks, after series of errors, or when user asks for session review, retrospective, lessons learned. Records improvements to backlog.
8SKILL.mdUpdated Apr 17, 2026
dmitryprg-ai/research
data-ai
VerifiedTrustedCommunity
Analyze data, investigate datasets, work with CSV/parquet/pandas/dataframes. Use when analyzing data, exploring datasets, running experiments, or when user mentions data, analysis, parquet, csv, pandas, dataframe, statistics, investigation.
8SKILL.mdUpdated Apr 17, 2026