Tech Debt
Use skill to generate boilerplate code, refactor legacy code, and write tests faster
Example: Generate React component with TypeScript types, styled-components, and comprehensive test suite in minutes
Reduce development time by 40-60% for repetitive coding tasks
Systematically review code for bugs, security issues, and style violations
Example: Analyze pull requests for common anti-patterns, suggest performance improvements, flag security vulnerabilities
Catch 70%+ of code issues before human review, improve code quality
Trace errors through stack traces and identify root causes faster
Example: Analyze error logs, suggest probable causes, recommend fixes with code examples
Cut debugging time by 30-50%, especially for unfamiliar codebases
Get explanations, examples, and best practices for unfamiliar frameworks
Example: Understand Next.js app router, learn Rust ownership, grasp Kubernetes concepts with practical examples
Accelerate learning curve by 2-3x, reduce onboarding time for new tech stacks
Submit your Claude Code skill and start earning
epx add Donchitos/Claude-Code-Game-Studios --skill tech-debtCompatible with
Supported agents
description: "Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling."
argument-hint: "[scan|add|prioritize|report]"
allowed-tools: Read, Glob, Grep, Write
| name | tech-debt |
| description | "Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling." |
| argument-hint | "[scan|add|prioritize|report]" |
| user-invocable | true |
| allowed-tools | Read, Glob, Grep, Write |
Determine the mode from the argument:
scan — Scan the codebase for tech debt indicatorsadd — Add a new tech debt entry manuallyprioritize — Re-prioritize the existing debt registerreport — Generate a summary report of current debt statusIf no subcommand is provided, output usage and stop. Verdict: FAIL — missing required subcommand.
Search the codebase for debt indicators:
TODO comments (count and categorize)FIXME comments (these are bugs disguised as debt)HACK comments (workarounds that need proper solutions)@deprecated markersCategorize each finding:
Present the findings to the user.
Ask: "May I write these findings to docs/tech-debt-register.md?"
If yes, update the register (append new entries, do not overwrite existing ones). Verdict: COMPLETE — scan findings written to register.
If no, stop here. Verdict: BLOCKED — user declined write.
Prompt for: description, category, affected files, estimated fix effort, impact if left unfixed.
Present the new entry to the user.
Ask: "May I append this entry to docs/tech-debt-register.md?"
If yes, append the entry. Verdict: COMPLETE — entry added to register.
If no, stop here. Verdict: BLOCKED — user declined write.
Read the debt register at docs/tech-debt-register.md.
Score each item by: (impact_if_unfixed × frequency_of_encounter) / fix_effort
Re-sort the register by priority score and recommend which items to include in the next sprint.
Present the re-prioritized register to the user.
Ask: "May I write the re-prioritized register back to docs/tech-debt-register.md?"
If yes, write the updated file. Verdict: COMPLETE — register re-prioritized and saved.
If no, stop here. Verdict: BLOCKED — user declined write.
Read the debt register. Generate summary statistics:
Flag any items that have been in the register for more than 3 sprints.
Output the report to the user. This mode is read-only — no files are written. Verdict: COMPLETE — debt report generated.
/sprint-plan to schedule high-priority debt items into the next sprint./tech-debt report at the start of each sprint to track debt trends over time.## Technical Debt Register
Last updated: [Date]
Total items: [N] | Estimated total effort: [T-shirt sizes summed]
| ID | Category | Description | Files | Effort | Impact | Priority | Added | Sprint |
|----|----------|-------------|-------|--------|--------|----------|-------|--------|
| TD-001 | [Cat] | [Description] | [files] | [S/M/L/XL] | [Low/Med/High/Critical] | [Score] | [Date] | [Sprint to fix or "Backlog"] |
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiontech-debtExecute the skills CLI command in your project's root directory to begin installation:
epx add Donchitos/Claude-Code-Game-Studios --skill tech-debtFetches tech-debt from Donchitos/Claude-Code-Game-Studios and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/tech-debt
Restart Cursor to activate tech-debt. Access via /tech-debtin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Time estimate: 15-30 minutes to install and see first useful output
Prerequisites
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use coding skills for boilerplate generation, code reviews, refactoring legacy code, writing tests, learning new frameworks, and debugging non-critical issues. Best for repetitive tasks where errors are easy to catch.
✗ Avoid when
Avoid for production security features (auth, encryption, payment processing), complex business logic requiring deep domain knowledge, performance-critical algorithms, or when learning fundamentals is more valuable than speed.
localize
Donchitos/Claude-Code-Game-Studios · Game Release · same repo
art-bible
Donchitos/Claude-Code-Game-Studios · Game Design · same repo
gate-check
Donchitos/Claude-Code-Game-Studios · Game QA & Testing · same repo
create-epics
Donchitos/Claude-Code-Game-Studios · Game Dev Planning · same repo
propagate-design-change
Donchitos/Claude-Code-Game-Studios · Game Design · same repo
caveman
JuliusBrussee/caveman · Marketing · 2 shared tags
Registry listing for tech-debt matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in tech-debt — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend tech-debt for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: tech-debt is focused, and the summary matches what you get after install.
I recommend tech-debt for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added tech-debt from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
tech-debt reduced setup friction for our internal harness; good balance of opinion and flexibility.
tech-debt has been reliable in day-to-day use. Documentation quality is above average for community skills.
tech-debt reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: tech-debt is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 46