audit-plugin

Audit plugin content

Deep analysis of all skills, agents, and commands in the whetstone plugin. Surfaces quality issues that degrade skill effectiveness, waste tokens, or confuse the model.

Scope

PLUGIN_DIR=plugins/whetstone
SYNC_LOG=docs/audit/audit-log.md

If $ARGUMENTS specifies a name or category, narrow to that. Otherwise audit everything. Normalize component names to the ia- prefix before using them as --skill/--component filters (e.g. debugging → ia-debugging). Exit code 2 from those commands means the filter matched nothing — almost always a missing prefix — not a validation failure; re-run with the prefixed name.

Reactive mode: If invoked after a skill/agent failed during use, detect the failing component from conversation context and focus the audit on that component first.

Phase 0: Pre-flight — read prior decision log

Read $SYNC_LOG in full before any checks run. Build an in-memory set of already-evaluated findings keyed by (component, issue-signature) across every run entry. Use it as a filter during Phase 3 presentation:

• Previously applied, exact match — drop silently.
• Previously rejected, exact match — drop silently unless new evidence contradicts the prior reason; if so, surface with a RE-EVALUATE flag and quote the prior rejection reason.
• Previously deferred, exact match — surface with a PREVIOUSLY DEFERRED tag and the original defer reason so the user can judge whether conditions have changed.
• No match — present normally.

While reading, also detect prune triggers and emit a one-line reminder at the end of Phase 3 if any fire:

• Any entry older than 30 days.
• Any entry referencing a component that no longer exists under $PLUGIN_DIR.
• Any entry whose reasoning has been superseded by a feedback-memory rule.

Reminder format: "Sync log has N prune candidates — run /prune-sync-log."

If $SYNC_LOG doesn't exist, note it and continue — the post-apply step in Phase 5b creates it.