agentleFS
neomjsneomjs/neo-agent-skills/.agents/skills/tech-debt-radar/SKILL.md

tech-debt-radar

Skill11 starsChanged yesterdayMITView on GitHub

Semantic RAG sweep for architectural technical debt; use during architectural analysis, proactive debt searches, auditing for abandoned logical loops, ambient debt scan requests, or PR reviews of major shifts.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If you need to sweep for ambient architectural debt, analyze historical epics, or mine the Memory Core for abandoned code flows, you MUST …

    line 8

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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 Radar

If you need to sweep for ambient architectural debt, analyze historical epics, or mine the Memory Core for abandoned code flows, you MUST immediately use the view_file tool to read and strictly adhere to .agents/skills/tech-debt-radar/references/tech-debt-radar-guide.md before proceeding.

What it enforces

Uses Frontier Model semantic RAG to sweep historical issues and Memory Core sessions during architectural analysis, proactive debt searches, repository audits for abandoned logical loops, or PR reviews of fundamental architectural shifts.

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.