techdebt
Tech Debt: Find and Kill
Build a /techdebt slash command and run it at the end of every session to find and kill duplicated code. — Claude Code team tip
Activation
When user invokes /techdebt or /techdebt [path]:
Analysis Process
1. Scope the Search
If $ARGUMENTS provided, focus on that path. Otherwise, analyze:
- Recently modified files (from git)
- The entire
src/or main source directory
# Get recently modified files
More from potatoman03/runbook
runbook
Claude Code productivity system based on tips from the Claude Code team. Provides commands for parallel worktrees, plan reviews, CLAUDE.md maintenance, tech debt hunting, auto-fixing, code grilling, elegant refactors, visual explanations, and subagent orchestration. Use when wanting to work more effectively with Claude Code.
5explain
Generate visual explanations of code, architecture, or concepts. Creates HTML presentations, ASCII diagrams, and interactive visualizations. Use for learning unfamiliar code or explaining to others.
1grill
Get grilled on your changes before making a PR. Claude acts as a rigorous reviewer, asking probing questions and not approving until you demonstrate understanding. Use to catch issues before they reach code review.
1elegant
Scrap a mediocre solution and implement the elegant one. Use after a fix feels hacky or over-complicated. Claude uses all accumulated context to find the right solution. Based on the prompting pattern from the Claude Code team.
1plan-review
Review a plan as a staff engineer would. Use when you have a plan and want rigorous feedback before implementation. Catches issues, suggests alternatives, and identifies risks. Based on the Claude Code team practice of having a second Claude review plans.
1subagents
Orchestrate subagents for complex tasks. Append "use subagents" to throw more compute at problems. Keep main context clean by offloading to specialized subagents. Based on the Claude Code team's subagent practices.
1