agentleFS
VladTheProgrammerVladTheProgrammer/claude-asimov/.claude/skills/audit-claude/SKILL.md

audit-claude

Skill0 starsChanged 4 months agoMITView on GitHub

Verify CLAUDE.md content is still accurate and still belongs there

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

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    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:

    Tool/version claims: check build files. Still the current version?

    line 12
  2. Distinctive:

    Path claims: check the path exists.

    line 13
  3. Distinctive:

    Behavioral claims: check 2-3 files that should follow the rule.

    line 14
  4. Distinctive:

    Should an unconditional rule become conditional, or vice versa?

    line 29
  5. Distinctive:

    Do NOT modify CLAUDE.md. Report only.

    line 40

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

Audit CLAUDE.md by checking every line against two criteria:

1. Still accurate?

For each concrete claim, verify against current code:

  • Import/package claims: grep for the pattern. Still used consistently?
  • Tool/version claims: check build files. Still the current version?
  • Path claims: check the path exists.
  • Behavioral claims: check 2-3 files that should follow the rule. Do they?

2. Still belongs here?

For each line, apply the CLAUDE.md admission test:

  • Is it obvious from reading the code? → Move to rule or remove.
  • Would I get it right from training? → Remove.
  • Is it scoped to one area (e.g. the API layer, the data pipeline, the UI)? → Move to path-scoped rule.
  • Is it duplicated in a rule file? → Remove from CLAUDE.md.

3. Conditional rules audit

For any <important-if {condition}>{rule}</important-if> blocks:

  • Is the condition still relevant? (Does the module/flag/target still exist?)
  • Is the rule inside still accurate?
  • Should an unconditional rule become conditional, or vice versa?

Output

A table with one row per CLAUDE.md line:

LineAccurate?Belongs here?Conditional?Action

Actions: KEEP, REMOVE (derivable), MOVE TO RULE (scoped), UPDATE (stale), WRAP IN CONDITION, UNWRAP CONDITION.

Do NOT modify CLAUDE.md. Report 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.