agentleFS
soophoosoophoo/skills/tidy/SKILL.md

tidy

Skill0 starsChanged 43 days agoNo licenceView on GitHub

Audit the project's context/ folder so it keeps telling the truth. Finds broken references (UC/AC/ADR/L ids that don't exist), ADR numbering problems, accepted ADRs the code no longer follows, stale or inconsistent build plans, briefs with overdue deferred items or a spec that drifted past their out-of-scope, lessons that are duplicated, already enforced or overdue for escalation, an oversized or stale memory.md, and CLAUDE.md commands that no longer exist. Reports a fix list grouped by file, applies only the fixes the user picks, and routes the rest to the skill that owns it. Never changes the code. Use every few weeks, before a large feature, when agents seem to follow outdated guidance, or whenever the user says "tidy", "clean up the context", "range le contexte", "is the context up to date", or "audit context".

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use retro.

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

    retro

    Conduct a retrospective on a coding session.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 18 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.

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.