agentleFS
Sign inStart free
garbageekgarbageek/claude-plugins/skills/audit-init/SKILL.md

audit-init

Skill1 starsChanged 35 days agoMITView on GitHub

Initialize the audit ticket workspace when the user explicitly requests audit lifecycle setup. Preserve existing records and report health and queues. Not a prerequisite for read-only code review.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the audit invocation contract.

    line 8
  2. Very specific:

    Run the CLI init, then doctor, then summary commands (or equivalent manually configured MCP tools).

    line 15
  3. Very specific:

    Do not silently apply doctor --fix, create tickets, or commit changes.

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Initialize Audit Workspace

Read the audit invocation contract. Resolve the installed plugin and target project separately. Use the bundled Python CLI after setting AUDIT_PLUGIN_ROOT and AUDIT_PROJECT_DIR to the observed paths. A separately configured audit_* MCP server is optional and requires an explicit absolute project root. Never create project state in the installed plugin directory.

Run the CLI init, then doctor, then summary commands (or equivalent manually configured MCP tools). Initialization is idempotent; preserve existing state. A read-only review or status question does not authorize initialization.

CLI sequence, after resolving the two paths above:

python3 "${AUDIT_PLUGIN_ROOT}/scripts/audit.py" --root "${AUDIT_PROJECT_DIR}" init
python3 "${AUDIT_PLUGIN_ROOT}/scripts/audit.py" --root "${AUDIT_PROJECT_DIR}" doctor
python3 "${AUDIT_PLUGIN_ROOT}/scripts/audit.py" --root "${AUDIT_PROJECT_DIR}" summary

Report the actual created or existing workspace, doctor findings, and queue. Do not silently apply doctor --fix, create tickets, or commit changes.

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.

Check your setup, free