Techdebt
Copier template that bootstraps AI-agent-optimized project setups: layered context routing, curated skills, and an enforced validation gate — synced across projects.
npx -y skills add SamyakJhaveri/loam --skill techdebtAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Scan codebase for tech debt: duplicated logic, dead code, magic numbers. Use at end of session before final commit for a broad codebase sweep. NOT for reviewing only recently changed code (use /simplify).
SKILL.md
0.9 KB, as published. Nobody here has run it
Scan recently changed files (git diff --name-only HEAD~5) for:
- Duplicated logic — consolidate into shared utility
- Dead code — unused imports/exports/functions (grep to verify before removing)
- Magic numbers/strings — extract to named constants
- Nested conditionals >3 levels — refactor with early returns
- TODO/FIXME — list but don't auto-fix without asking
For each finding: file:line, category, description, proposed fix Ask before applying fixes that touch >3 files. After fixes: run the project's type checker or linter to confirm no regressions.
Gives 0 of the 12 instructions most refactoring skills give
Counted across 521 of the 525 authors here whose files we hold, read 2026-08-06
- run tests after each changein 59 of 521, across 56 files
- write tests before refactoringin 27 of 521, across 24 files
- preserve external behaviorin 26 of 521, across 22 files
- remove dead codein 25 of 521, across 24 files
- make small incremental changesin 20 of 521, across 17 files
- break the implementation into tiny commitsin 18 of 521, across 5 files
- ask the user about alternative optionsin 17 of 521, across 4 files
- create a GitHub issue with the planin 17 of 521, across 4 files
- explore the repository to verify assertionsin 17 of 521, across 4 files
- interview the user about the refactorin 16 of 521, across 3 files
- check the codebase for test coveragein 16 of 521, across 3 files
- refactor one thing at a timein 16 of 521, across 12 files
Said here and by no other author read
- refactor nested conditionals deeper than three levels
- report TODO and FIXME comments
- ask before applying fixes that touch more than three files
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.