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

audit-next

Skill1 starsChanged 35 days agoMITView on GitHub

Find the next eligible ticket for resolution or independent verification in an existing audit workspace. Use for queue selection without changing state.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    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:

    Use the requested queue (resolution or verification).

    line 15

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

Select the Next Audit Ticket

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.

Use the requested queue (resolution or verification); without a choice, show both. If no audit workspace exists, report it without initialization. Run the next CLI command; this selects work but does not execute it.

python3 "${AUDIT_PLUGIN_ROOT}/scripts/audit.py" --root "${AUDIT_PROJECT_DIR}" next --for resolution --json
python3 "${AUDIT_PLUGIN_ROOT}/scripts/audit.py" --root "${AUDIT_PROJECT_DIR}" next --for verification --json

Show the returned ticket ID, status, severity, title and selection reason. For resolution, surface related_tickets as optional same-file/fix-group suggestions, not as automatic work. They have already passed FIX/dependency eligibility. State an empty queue accurately. Do not claim a blocked ticket ready or automatically start resolution/verification from a queue-inspection request.

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