agentleFS
garbageekgarbageek/claude-plugins/skills/audit-verification/SKILL.md

audit-verification

Skill1 starsChanged 35 days agoMITView on GitHub

Use when resolved audit tickets need independent verification. Default to the next READY_FOR_VERIFICATION ticket. Verification may write PASS/PARTIAL/FAIL with criterion evidence; it should not edit implementation code.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    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. Very specific:

    Read the runtime invocation contract first.

    line 9
  2. Distinctive:

    If this agent/session implemented the fix, hand verification to a fresh native subagent or another session with this skill, the project …

    line 13
  3. Distinctive:

    Use the shared resolution proof guide to separate proposed checks, observed results, and verdicts, including whether corrected source is …

    line 20
  4. Distinctive:

    If the workspace is absent or no ticket is returned, report that state without initializing it.

    line 29
  5. Distinctive:

    read ticket, verification record, code, and resolution evidence.

    line 43
  6. Distinctive:

    run independent checks/commands needed to validate the result.

    line 44
  7. Distinctive:

    do not edit implementation code.

    line 49
  8. Distinctive:

    do not perform resolution work.

    line 50
  9. Very specific:

    do not mark PASS without criterion evidence and a verified commit.

    line 51
  10. Distinctive:

    do not invent missing acceptance criteria.

    line 52
  11. Distinctive:

    Stop after writing the independent verdict and summarize the reason.

    line 56

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

Audit Verification

Read the runtime invocation contract first. Use the bundled Python CLI after resolving AUDIT_PLUGIN_ROOT and AUDIT_PROJECT_DIR as described there. A separately configured audit_* MCP server is an optional equivalent with an explicit absolute root.

Purpose: independently verify resolved tickets against the original acceptance criteria and current code state.

If this agent/session implemented the fix, hand verification to a fresh native subagent or another session with this skill, the project root, ticket IDs, fix revision, and original criteria. Do not treat switching the role name as independent verification. Without an independent reviewer, leave the ticket awaiting verification and report the handoff; do not write PASS.

Use the shared resolution proof guide to separate proposed checks, observed results, and verdicts, including whether corrected source is active in the relevant running instance. Keep the existing acceptance gates and user-authorized validation scope; do not generate tests or restart services implicitly.

First move from empty context

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

If the workspace is absent or no ticket is returned, report that state without initializing it. Do not create or resolve tickets. Diagnose malformed records rather than treating a failed queue command as an empty queue.

PASS flow

python3 "${AUDIT_PLUGIN_ROOT}/scripts/audit.py" --root "${AUDIT_PROJECT_DIR}" show 001
# inspect code and evidence independently
python3 "${AUDIT_PLUGIN_ROOT}/scripts/audit.py" --root "${AUDIT_PROJECT_DIR}" verify 001   --status PASS   --verified-commit def456   --criterion "AC1: pass - null-user payload returns typed validation error"   --evidence "Manual reproducer no longer fails"   --test "manual reproducer: pass"   --verdict "All acceptance criteria satisfied"   --as audit-verification   --json

Repeat --criterion once per single-line result using the original unique AC IDs. Evidence, the executed check/result, and the verdict must be meaningful in the active record; placeholder text or quoted examples do not satisfy PASS. Use PARTIAL or FAIL when evidence is incomplete or a criterion is not satisfied. Do not replace an existing verification file with the reference template.

Allowed actions

  • read ticket, verification record, code, and resolution evidence;
  • run independent checks/commands needed to validate the result;
  • set PASS, PARTIAL, FAIL, REGRESS, BLOCKED, WONTFIX, or INVALID through python3 "${AUDIT_PLUGIN_ROOT}/scripts/audit.py" --root "${AUDIT_PROJECT_DIR}" verify.

Forbidden actions

  • do not edit implementation code;
  • do not perform resolution work;
  • do not mark PASS without criterion evidence and a verified commit;
  • do not invent missing acceptance criteria.

Stop condition

Stop after writing the independent verdict and summarize the reason.

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.