techdebt
Skill1 starsChanged 3 days agoMITView on GitHub
End-of-session tech debt cleanup. Scans for TODOs, dead code, unused imports, type issues, and quick wins before you log off.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- jh941213/my-cc-harnesstheir own version, first seen Nov 1, 2026
- jh941213/ADLC-harnesstheir own version, first seen Nov 1, 2026
- LucasCooperBey/claude-skillsword for word, first seen Oct 20, 2026
- mikezamayias/agent-skillstheir own version, first seen Oct 11, 2026
- DoubleML/doubleml-for-pytheir own version, first seen Oct 8, 2026
- jh941213/my-claude-code-assettheir own version, first seen Oct 8, 2026
Used with
Projects with it also use docs-ci, docs-interfaces and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
jh941213Skilldocs-ci
문서 CI(링크·OpenAPI lint·breaking 게이트·mermaid 검증)나 문서 드리프트 감지(docs.yaml 신선도 검사)를 설치하거나 돌릴 때 사용. 문서 내용 작성은 docs-architecture·docs-interfaces·docs-manuals.
Also in 3 projects that use this
jh941213Skilldocs-interfaces
API·이벤트 인터페이스 문서(OpenAPI·swagger·AsyncAPI 명세, 엔드포인트 레퍼런스, API 구성도·시퀀스, API CHANGELOG)를 만들거나 코드와 맞출 때 사용. 시스템 구성도는 docs-architecture, API 설계 원칙은 api-design-principles.
Also in 3 projects that use this
RachaelQuiselSkillclient-docs
Client documentation. Use when a build needs documentation updates or missing project documents need to be identified.
Also in 3 projects that use this
planailabsSkilldocs-architecture
Layout, build pipeline, and structural gotchas for this dual-Astro repo. Read before changing structure, routing, or adding content. Operational/dev-server questions → dev-build skill.
Also in 3 projects that use this
llama-farmSkillcommit-push-pr
Commit changes, push to GitHub, and open a PR. Includes quality checks (security, patterns, simplification). Use --quick to skip checks.
Also in 5 projects that use this
diego-tobalinaSkillbuild-fix
Fix build and compilation errors systematically. Run when build fails.
Also in 3 projects that use this
- +4 more from jh941213
Other versions14 projects use a version of this.
Word for word · 1
- LucasCooperBey/claude-skills★ 1100% same
Edited · 0
None found.
Wrote their own version · 13
- DoubleML/doubleml-for-py★ 798same name
- DataDog/dd-trace-java★ 739same name
- chenzhen7/akari★ 189same name
- jh941213/ADLC-harness★ 125same name
- jh941213/my-cc-harness★ 125same name
- jh941213/my-claude-code-asset★ 125same name
- aromanarguello/roman-skills★ 18same name
- rayketcham-lab/qn-claude-web★ 2same name
- almax000/claude-skills★ 1same name
- mikezamayias/agent-skills★ 1same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository53 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/deep-recon/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- adversarial-researchSkill
- algorithmic-artSkill
- api-integrationSkill
- breakdownSkill
- c4-architectSkill
- canvas-designSkill
- coding-agentsSkill
- compound-engineeringSkill
- context-budgetSkill
- counterfactualSkill
- critiqueSkill
- d3js-visualizationSkill
- data-analyst-agentSkill
- database-migrationsSkill
- deep-reconSkill
- design-tasteSkill
- e2b-sandboxSkill
- ecosystem-auditSkill
- executing-plansSkill
- frontend-designSkill
- fullstack-agentSkill
- grillSkill
- kickoffSkill
- mcp-builderSkill
- model-migrationSkill
- naming-the-machineSkill
- full-output-enforcementSkill
- package-researchSkill
- pdf-generationSkill
- pp2pSkill
- pp3pSkill
- prompt-engineerSkill
- prompt-groundingSkill
- redesignSkill
- requesting-code-reviewSkill
- reverse-engineer-to-learnSkill
- review-changesSkill
- scratchpadSkill
- shipSkill
- slack-gif-creatorSkill
- sprint-architectSkill
- test-and-fixSkill
- threat-modelSkill
- verification-before-completionSkill
- visual-verdictSkill
- webapp-testingSkill
- web-asset-generatorSkill
- whatdidimissSkill
- wiki-writeSkill
- writing-plansSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Before creating a PR
- Distinctive: line 14
After a big feature merge
- Very specific: line 18
When the user invokes /techdebt:
- Very specific: line 31
If no changes, scan the whole project's src/ directory.
- Distinctive: line 79
Delete commented-out code (if > 30 days old per git blame)
- Distinctive: line 80
Remove unused local variables
- Very specific: line 109
Check for new files in ~/.claude/artifacts/research/ that aren't in ~/.claude/artifacts/research/INDEX.md:
- Distinctive: line 116
If any unindexed files found, append them to the appropriate section in INDEX.md with channel tag.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Tech Debt (/techdebt)
End-of-session codebase cleanup scan.
When to Use
- End of a coding session
- Before creating a PR
- Periodic hygiene check
- After a big feature merge
Instructions
When the user invokes /techdebt:
Step 1: Identify Scope
Determine what to scan:
# Files modified this session (since last commit on main)
BASELINE=$(git merge-base HEAD main 2>/dev/null || echo "HEAD~10")
git diff --name-only $BASELINE HEAD
git diff --name-only # Unstaged tooIf no changes, scan the whole project's src/ directory.
Step 2: Run Parallel Scans
Scan 1 — TODOs and FIXMEs (grep for actionable items):
grep -rn "TODO\|FIXME\|HACK\|XXX\|WORKAROUND" src/ --include="*.ts" --include="*.tsx"Categorize each:
- Stale (> 30 days, check git blame)
- Actionable now (< 5 min fix)
- Needs ticket (complex, track separately)
Scan 2 — Dead Code (Task tool, subagent_type: "general-purpose"):
Scan these files for dead code:
[file list]
Find:
- Unused exports (exported but never imported)
- Unused functions/variables
- Unreachable code paths
- Commented-out code blocks
- Unused imports
Return file:line for each finding.Scan 3 — Type Safety (Task tool, subagent_type: "general-purpose"):
Scan these files for type safety issues:
[file list]
Find:
- `as` type assertions that could fail at runtime
- Missing null checks
- Implicit `any` from untyped dependencies
- Type guards that don't fully narrow
- Union types that aren't exhaustively handled
Return file:line and severity for each.Step 3: Quick Wins
Automatically fix items that are safe:
- Remove unused imports
- Delete commented-out code (if > 30 days old per git blame)
- Remove unused local variables
- Fix obvious type narrowing gaps
Step 4: Report
## Tech Debt Report
### Auto-Fixed
- Removed N unused imports
- Deleted N lines of dead code
- Fixed N type issues
### Needs Attention
| File | Issue | Effort |
|------|-------|--------|
| src/foo.ts:42 | Stale TODO from 2 months ago | 5 min |
| src/bar.ts:17 | Type assertion could fail | 15 min |
### TODOs Summary
- N stale (> 30 days)
- N actionable now
- N need tickets
### Health Score: X/10Step 4b: Research Artifact Index Sweep
Check for new files in ~/.claude/artifacts/research/ that aren't in ~/.claude/artifacts/research/INDEX.md:
# Find files newer than INDEX.md
find ~/.claude/artifacts/research/ -name "*.md" -newer ~/.claude/artifacts/research/INDEX.md ! -name "INDEX.md" 2>/dev/nullIf any unindexed files found, append them to the appropriate section in INDEX.md with channel tag. Report: "INDEX.md: added N new research artifacts."
Step 5: Offer Next Steps
Would you like me to:
A) Fix the "Needs Attention" items now
B) Create GitHub issues for the complex ones
C) Just note it and move onArguments
| Arg | Effect |
--fix-all | Auto-fix everything safe, no prompt |
--report-only | No fixes, just report |
--scope "dir" | Scan specific directory |
Source
Inspired by Boris Cherny's Claude Code tips (https://x.com/bcherny/status/2017742741636321619), the tip "Build a /techdebt slash command and run it at the end of every session".
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

