tech-debt
Skill1 starsChanged 5 months agoApache-2.0View on GitHub
Scan codebase for technical debt and create GitHub Issues for high-severity findings
38 other projects use a version of this.
Adopted by
Most recently taken up by
- pantheon-org/tekhnetheir own version, first seen Nov 15, 2026
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- y-miyazaki/configtheir own version, first seen Nov 14, 2026
- Donchitos/Claude-Code-Game-Studiostheir own version, first seen Nov 9, 2026
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- dirien/yet-another-agent-harnesstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use playtest-report, soak-test and 10 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.
CoralGameSkillplaytest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
Also in 13 projects that use this
lilangMaxSkillsoak-test
Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.
Also in 10 projects that use this
lilangMaxSkillteam-live-ops
Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.
Also in 10 projects that use this
CoralGameSkillteam-audio
Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.
Also in 13 projects that use this
- +6 more from lilangMax
- +2 more from CoralGame
Other versions38 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 38
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- anthropics/knowledge-work-plugins★ 36ksame name
- vm0-ai/vm0★ 1.2ksame name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- striderZA/OpenCodeGameStudios★ 124same name
- tranhieutt/software_development_department★ 71same name
- cenconq25/claude-code-app-studio★ 40same name
- drafthq/draft★ 40same name
- fagemx/edda★ 36same name
- CoralGame/Claude-Code-Game-Studios★ 19same name
28 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 repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- auditSkill
- decomposeSkill
- dev-allSkill
- dev-investigateSkill
- devSkill
- digSkill
- investigateSkill
- prSkill
- reviewSkill
- update-docsSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 31 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 58
Test files with no assertions
“Common” is measured: kept by at least 6 in 10 of the 31 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 — Technical Debt Scanner
Scan the codebase for technical debt and refactoring opportunities, then create GitHub Issues for actionable items.
Steps
- Scan the codebase for the patterns listed below
- For each finding, assess severity (High / Medium / Low) and effort (S / M / L)
- Group findings by category
- For High severity items, create GitHub Issues using
gh issue create - Output a summary report
Detection Patterns
Code Smells
- Duplicated code (3+ similar blocks)
- Long functions (50+ lines)
- Large files (500+ lines)
- Deep nesting (4+ levels)
- God classes (too many responsibilities)
- Dead code (unused functions, imports, variables)
- TODO/FIXME/HACK comments left in code
Architecture
- Circular dependencies between modules
- Layer violations (check CLAUDE.md for architecture boundaries)
- Missing abstractions (concrete classes where interfaces should be)
- Inconsistent patterns across similar features
Performance
- N+1 queries
- Missing database indexes on frequently queried columns
- Unbounded lists without pagination
- Heavy computation on main thread
- Memory leaks (retain cycles, leaked references)
Testing
- Public functions without unit tests
- Test files with no assertions
- Missing edge case coverage (null, empty, boundary values)
Dependencies
- Outdated dependencies (check against latest stable versions)
- Deprecated API usage
- Security vulnerabilities in dependencies (if audit tools available)
Issue Creation
For each High severity finding:
gh issue create \
--title "Tech Debt: {concise description}" \
--body "{detailed description with file locations and suggested fix}" \
--label "tech-debt"Output Format
## Tech Debt Report
**Scanned:** N files
**Findings:** X High, Y Medium, Z Low
**Issues created:** N
### High Severity
| # | Category | File | Description | Effort | Issue |
|---|----------|------|-------------|--------|-------|
### Medium Severity
| # | Category | File | Description | Effort |
|---|----------|------|-------------|--------|
### Low Severity
(summary only)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.

