tech-debt
Skill1 starsChanged 10 days agoApache-2.0View on GitHub
Discover and classify technical debt from mechanical signals; apply closed-set fixes when requested. Use in conversation when the user asks to survey or fix safe documentation/dependency debt. Also the loop entry skill for scheduled scans or detect JSON. Interactive default is survey only; write agent_report_file and apply closed-set fixes when the request asks for changes to be made (for example fix, apply, or update) or automation sets agent_edit_allowed in Constraints. Do not apply structural refactors.
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
- 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
- striderZA/OpenCodeGameStudiostheir own version, first seen Nov 4, 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 12 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 9 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 9 projects that use this
CoralGameSkillteam-polish
Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.
Also in 14 projects that use this
- +5 more from lilangMax
- +3 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 repository56 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .apm/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .github/workflows/CLAUDE.mdCLAUDE.md
- .cursor/rules/agent-skills.mdcCursor rule
- .cursor/rules/bats.mdcCursor rule
- .cursor/rules/github-actions-workflow.mdcCursor rule
- .cursor/rules/go.mdcCursor rule
- .cursor/rules/go-test.mdcCursor rule
- .cursor/rules/instructions.mdcCursor rule
- .cursor/rules/markdown.mdcCursor rule
- .cursor/rules/shell-script.mdcCursor rule
- .cursor/rules/terraform.mdcCursor rule
- agent-skills-reviewSkill
- changelogSkill
- ci-sweeperSkill
- docs-creatorSkill
- docs-updaterSkill
- github-actions-reviewSkill
- github-actions-validationSkill
- github-issue-autofixSkill
- github-issue-triageSkill
- github-pr-bodySkill
- github-pr-reviewSkill
- github-pr-reviseSkill
- go-reviewSkill
- go-validationSkill
- instructions-reviewSkill
- loop-verifierSkill
- markdown-validationSkill
- refactorSkill
- shell-script-reviewSkill
- shell-script-validationSkill
- tech-debtSkill
- test-gapSkill
- agent-skills-reviewSkill
- changelogSkill
- ci-sweeperSkill
- docs-creatorSkill
- docs-updaterSkill
- github-actions-reviewSkill
- github-actions-validationSkill
- github-issue-autofixSkill
- github-issue-triageSkill
- github-pr-bodySkill
- github-pr-reviewSkill
- github-pr-reviseSkill
- go-reviewSkill
- go-validationSkill
- instructions-reviewSkill
- loop-verifierSkill
- markdown-validationSkill
- refactorSkill
- shell-script-reviewSkill
- shell-script-validationSkill
- test-gapSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 70
When intent is unclear, survey and offer to apply — edits are harder to undo than a report.
- Very specific: line 76
Read previous_report when set.
- Very specific: line 78
IF agent_edit_allowed is false → emit survey shape with ### Candidates and optional ### Watch.
“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
UTILITY SKILL — technical debt survey and closed-set apply, not structural refactor.
Input
- Interactive (required): natural-language request; optional paths/signals — constraints in
## Constraintsor category-scope.md - Automation (optional): detect JSON in prompt — from a caller or optional skill detect script; not required for interactive runs. Read
agent_edit_allowed,agent_edit_target, andagent_report_filefrom## Constraintsper category-automation-envelope.md
Path allowlist, when present, arrives in ## Constraints.
Output Specification
Tech-debt report per common-output-format.md. Survey shape when agent_report_file is not written; apply shape when written — within category-scope.md.
Execution Scope
USE FOR:
- Classify mechanical
signals[]andhotspots[]into prioritized debt findings - Survey: emit Candidates with Delegate hints per taxonomy
- Apply: write
agent_report_file; apply closed-set fixes (broken_doc_ref,stale_doc, simplepin_drift) within allowlist
DO NOT USE FOR:
- Structural refactors or architecture changes
- CI repair
- Security remediation beyond reporting
- Edit caller state files (owned by the caller after verification)
Reference Files Guide
- category-debt-taxonomy.md (always read)
- common-checklist.md (always read)
- common-output-format.md (always read)
- category-scope.md (always read)
- category-detect-scope.md (read on interactive path)
- category-input-schema.md (read when detect JSON is present or the optional detect script is run)
- category-automation-envelope.md (read on automation path)
- common-troubleshooting.md (read on failure)
- Previous report at
previous_report(read when previous_report path exists) - category-pr-body-links.md (read when synthesizing the PR body)
assets/pr-body-template.mdandassets/pr-body-template-survey.md(read when synthesizing the PR body)
Workflow
Resolve agent_edit_allowed before classifying signals:
| Source | agent_edit_allowed |
| Interactive — default: the request asks to look, check, triage, or survey, or only names the skill | false — survey only; do not write agent_report_file or edit files |
| Interactive — the request asks for changes to be made (for example fix, apply, 修正して, 適用して, update, add) | true |
| Interactive — follow-up after a survey asking to apply | true |
Automation — ## Constraints | agent_edit_allowed: true or agent_edit_allowed: false from category-automation-envelope.md |
When intent is unclear, survey and offer to apply — edits are harder to undo than a report.
When agent_edit_allowed is true, resolve agent_edit_target and agent_report_file: on the interactive path use agent_edit_target: report and agent_report_file from detect JSON (agent_report_file field) or the user request; on the automation path read both from ## Constraints. Do not branch on other caller metadata outside ## Constraints. Load category-scope.md closed-set rules before any agent_report_file write or fix.
- Resolve scope (category-scope.md). Parse detect JSON when present; otherwise resolve the detect universe from the prompt (category-detect-scope.md), run this skill's optional detect script with the resolved
--scope(defaultall), then Agent-complement beyond mechanical output; if tools for detect are unavailable, gather signals/hotspots from the user request and repository tools instead of silent no-op. Load category-input-schema.md when parsing detect output. On detect script non-zero exit, read stdout and stop. - On the automation path, read category-automation-envelope.md for Constraints, PR templates, and Session Metrics.
- Read
previous_reportwhen set. Compare per common-checklist.md EVID-02. IF detect reportsskipOR bothsignalsandhotspotsare empty after gathering → emit survey no-op per common-output-format.md (Overview explains no-op); on automation path append## Session Metricsper category-automation-envelope.md; stop. - For each signal/hotspot, read ±30 lines (EVID-01). Classify per category-debt-taxonomy.md. Assign Delegate (CLASS-02).
- IF
agent_edit_allowedisfalse→ emit survey shape with### Candidatesand optional### Watch; on automation path loadassets/pr-body-template-survey.mdat synthesis and append## Session Metricsper category-automation-envelope.md; stop — do not writeagent_report_file. - ELSE IF
agent_edit_allowedistrueANDagent_edit_targetis notreport→ emit survey shape; note expectedagent_edit_target: reportin Overview; stop — do not writeagent_report_file. - ELSE IF
agent_edit_targetisreportAND (agent_report_fileis missing OR empty):- Automation path → emit survey shape; note missing
agent_report_filein Overview; stop. - Interactive path → apply closed-set fixes only (EDIT-01) per category-scope.md without writing a report file; emit apply shape (
### Changeslists only fixed paths); note in Overview that no report file was written because no path was given. When no closed-set fix applies either, emit survey shape and offer to write the report once the user names a path.
- Automation path → emit survey shape; note missing
- ELSE (
agent_edit_allowedistrueANDagent_edit_targetisreportANDagent_report_fileis set) → writeagent_report_filewithin allowlist with full persisted structure; apply closed-set fixes only (EDIT-01) per category-scope.md; emit apply shape with### Changes, optional### Deferred, and## Verification; on automation path loadassets/pr-body-template.mdat synthesis and append## Session Metricsper category-automation-envelope.md.
Error Handling
| Condition | Severity | Action |
Detect script non-zero exit or status: "error" (when invoked) | Fatal | Read stdout; stop — do not treat as success-path detect JSON |
skip or empty signals/hotspots | Info | Emit survey no-op (Overview explains no-op); stop |
| Path outside allowlist/denylist | Recoverable | Classify Watch; do not edit |
agent_report_file outside allowlist or on denylist | Recoverable | Do not write the report file; note in Overview; continue closed-set fixes within allowlist |
previous_report path missing | Recoverable | Skip comparison; note in Overview |
Edit requested but ## Constraints set agent_edit_allowed: false | Info | Survey only; note that the caller Constraints disallow edits |
agent_edit_allowed true with agent_edit_target not report | Recoverable | Survey only; note expected agent_edit_target: report |
agent_edit_allowed true with missing agent_report_file when agent_edit_target: report | Recoverable | Automation: survey only; note missing agent_report_file. Interactive: closed-set fixes only, no report file; note in Overview |
| Cap exceeded (>25 Critical+High-Priority) | Recoverable | Retain Critical first; defer overflow to Watch; note truncation |
Examples
- Prompt:
Survey technical debt from detect JSON - Result: Survey report per references/common-output-format.md; write
agent_report_fileonly whenagent_edit_allowedis true andagent_edit_targetisreport.
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.

