agentleFS
rioX432rioX432/agent-witness/.claude/skills/tech-debt/SKILL.md

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

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.
  • CoralGameSkill

    playtest-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

  • lilangMaxSkill

    soak-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

  • lilangMaxSkill

    team-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

  • CoralGameSkill

    team-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

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
  1. Distinctive:

    Test files with no assertions

    line 58

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/tech-debt — Technical Debt Scanner

Scan the codebase for technical debt and refactoring opportunities, then create GitHub Issues for actionable items.

Steps

  1. Scan the codebase for the patterns listed below
  2. For each finding, assess severity (High / Medium / Low) and effort (S / M / L)
  3. Group findings by category
  4. For High severity items, create GitHub Issues using gh issue create
  5. 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)

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.