dmitryprg-ai/techdebt-scan
.cursor/skills/techdebt-scan/SKILL.md
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.
$ 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.4s3 files scanned
SKILL.md
- name:
- techdebt-scan
- description:
- 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.
- disable-model-invocation:
- true
Technical Debt Scanner
Find and safely fix technical debt using TDD approach.
Order: SCAN -> TEST CASES -> REFACTOR -> VERIFY (do NOT skip steps!)
Phase 1: SCAN
Run scan scripts:
bash .cursor/skills/techdebt-scan/scripts/scan-large-files.sh
bash .cursor/skills/techdebt-scan/scripts/find-todos.sh
Then check for:
- Files > 300 lines (routes, services, components > 200 lines)
- Duplicated code patterns (grep for identical blocks > 5 lines)
- Functions > 50 lines
- Deep nesting (> 3 levels)
- Files with > 10 exports
- Magic numbers/strings
Scan Results Template
## TECHDEBT SCAN RESULTS — [date]
### Oversized Files
| File | Lines | Limit | Severity |
|------|-------|-------|----------|
| <path> | X | Y | HIGH/MED |
### Duplicate Code
| Pattern | File 1 | File 2 | Lines | Severity |
|---------|--------|--------|-------|----------|
| <desc> | <path> | <path> | X | HIGH/MED |
### Code Smells
| Type | Location | Description | Severity |
|------|----------|-------------|----------|
| Long function | <path>:<line> | X lines | MED |
### Exceptions (NOT violations)
| File | Exception Type | Reason |
|------|---------------|--------|
| <path> | High Cohesion Monolith | <reason> |
High Cohesion Monolith criteria:
- Single business responsibility (not a god-object)
- High method cohesion -- methods share common state
- Splitting requires full test coverage for safety
Phase 2: PRIORITIZE
| Severity | Impact | Effort | Priority | |----------|--------|--------|----------| | HIGH | Blocks development | Low | P0 -- Fix now | | HIGH | Blocks development | High | P1 -- Plan | | MED | Reduces quality | Low | P2 -- Quick win | | MED | Reduces quality | High | P3 -- Backlog | | LOW | Cosmetic | Any | P4 -- Optional |
Phase 3: TEST CASES (MANDATORY before refactoring)
Write tests BEFORE any code changes. 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
## TECHDEBT FIX VERIFICATION
| ID | Description | Tests Written | Tests Passing | Status |
|----|-------------|---------------|---------------|--------|
| D1 | <desc> | X | X | OK |
- [ ] `npm run build` -- success
- [ ] `npm run lint` -- 0 errors
- [ ] `npm test` -- all passing
FORBIDDEN
- Refactoring without SCAN first
- Refactoring without TEST CASES
- Writing tests AFTER refactoring
- "Build passed = everything works"
Related Skills
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
dmitryprg-ai/refactoring
development
VerifiedTrustedCommunity
Improve code structure without changing behavior. Use when refactoring, cleaning up, optimizing, simplifying, extracting methods, or reducing complexity. Requires tests BEFORE refactoring, small steps, commit after each green test.
8SKILL.mdUpdated Apr 17, 2026