agentleFS
elfrostelfrost/ai-patchlab/.agents/skills/audit-project/SKILL.md

audit-project

Skill1 starsChanged 30 days agoMITView on GitHub

Audit the project runtime docs and scaffolding for drift or missing setup. Use when the user asks for a project audit, wants AGENTS or CLAUDE cleaned up, or needs to check whether the repository still matches EzProject conventions.

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Write AGENTS.md.proposed when the current document needs improvement.

    line 27
  2. Distinctive:

    If CLAUDE.md exists and is out of sync, call that out and propose matching updates.

    line 28
  3. Distinctive:

    Do not overwrite runtime docs without confirmation.

    line 32

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

Audit Project

Audit the project instructions and supporting scaffold, then propose precise updates.

Workflow

  1. Read:
    • AGENTS.md
    • CLAUDE.md if present
    • ROADMAP.md
    • DECISIONS.md
    • README.md
    • .ezproject.json if present
  2. Explore the codebase, dependencies, test setup, MCP config, and project structure.
  3. Score the runtime docs on:
    • project context
    • directory map
    • coding standards
    • common commands
    • testing guidance
    • architecture notes
    • gotchas
  4. Write AGENTS.md.proposed when the current document needs improvement.
  5. If CLAUDE.md exists and is out of sync, call that out and propose matching updates.
  6. Report missing EzProject infrastructure and suggest what should be installed or refreshed.

Rules

  • Do not overwrite runtime docs without confirmation.
  • Preserve project-specific details that are already correct.
  • Be direct about weak sections or stale content.

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.