/audit

description: "Umbrella for the audit family — the canonical way to run every sub-audit: '/audit knowledge' (scan memory and plans for extractable knowledge, backlog-to-promotion review), '/audit config' (CLAUDE.md/settings/docs drift and staleness), '/audit style' (mine session-log history for revealed working-style rules), '/audit usage' (value/ROI report over your own corpus), '/audit rules' (mine your distilled corrections for promotable standing rules), or '/audit share' (batch-review personal knowledge for promotion to the team-shared tier). Trigger: '/audit', 'run an audit', 'knowledge audit', 'config audit', 'audit my style', 'audit my rules', 'usage report', 'share knowledge', 'promote to team'."

/audit — Audit Family Dispatcher

A thin umbrella over the six sub-audits. `/audit` does not scan anything itself — it resolves which sub-audit(s) the user means, then delegates to the sub-skill that owns the actual work. Think of it as a menu + router, not another audit implementation. **The `/audit <verb>` forms are the canonical invocations for the whole family** (see "Canonical forms and compatibility" below).

Step 0: Parse the Verb (+ passthrough arguments)

`/audit` takes a **verb followed by optional arguments**. Resolve the FIRST token against the grammar below before doing anything else. **Arguments are legal only AFTER a recognized verb** — any remaining tokens after a recognized verb are passed through to the sub-skill unchanged (e.g. `/audit style recent`, `/audit rules promote R1 R3`). An unrecognized first token always hits the unknown-verb branch, exactly as before — passthrough never weakens the never-silently-guess rule.

| Input | Resolution | |---|---| | `/audit` (bare, no argument) | Present the **bare-menu** (Step 1) and wait for a pick. | | `/audit knowledge [args…]` | Delegate to `audit-knowledge` with the args (Step 2). | | `/audit config [args…]` | Delegate to `audit-config` with the args (Step 2). | | `/audit style [args…]` | Delegate to `audit-style` with the args (Step 2). Style is **opt-in only** — see the note at the end of this section. | | `/audit usage [args…]` | Delegate to `audit-usage` with the args (Step 2). Usage is **opt-in only** — same note as style. | | `/audit rules [args…]` | Delegate to `audit-rules` with the args (Step 2) — e.g. `/audit rules promote R1 R3`. Rules is **opt-in only** — same note as style. | | `/audit share [args…]` | Delegate to `audit-share` with the args (Step 2) — batch-review personal knowledge for promotion to the team-shared tier. Share is **opt-in only** — same note as style, and it additionally requires the shared-knowledge config (`projects_enabled` plus a non-empty `projects_shared_knowledge`). | | anything else (unrecognized verb) | **Unknown-verb branch** — do not guess or silently fall through. List the valid verbs and stop: *"'{verb}' is not a valid /audit sub-command. Valid verbs: knowledge, config, style, usage, rules, share. Run bare `/audit` for a menu."* |

**Style, usage, rules and share are opt-in, never routine.** They run only when explicitly selected — the user types the `/audit <verb>` form directly, or picks it off the bare-menu in Step 1. None of the four is ever fired automatically by the SessionStart audit-cadence nudge the way `/audit knowledge` and `/audit config` can be — session-start cadence checks are a knowledge/config concern; style-mining, usage reporting, rule-mining and cross-tier sharing stay deliberate, explicit actions every time. Share carries the strongest form of this: it writes into a team-shared and possibly public repo, so it is never anything but an explicit, per-item choice.

Step 1: Bare `/audit` — Present the Menu

When invoked with no argument, present the options and wait for the user to pick one before doing anything else:

> **Which audit?** > 1. `knowledge` — scan Claude memory and plans for extractable knowledge (backlog → promotion review) > 2. `config` — check CLAUDE.md files, plugin manifests, and knowledge docs for drift and staleness > 3. `style` — mine session-log history for revealed working-style rules (opt-in — not part of routine cadence) > 4. `usage` — value/ROI report for your own corpus (cost + quality + trends; opt-in — not routine cadence) > 5. `rules` — mine your distilled corrections for promotable standing rules (opt-in — not routine cadence) > 6. `share` — batch-review personal knowledge for promotion to the team-shared tier (opt-in; requires the shared-knowledge config)

Do not default to any one sub-audit and do not run anything before the user picks. A bare `/audit` with no reply is a no-op — exit cleanly, nothing was scanned.

Step 2: Delegate to a Resolved Sub-Skill

Once a verb is resolved (from Step 0's direct-invocation column or Step 1's menu pick), delegate to the matching sub-skill via the `Skill` tool, **passing through any trailing arguments from the invocation** — the sub-skill runs its own full step sequence (config resolution, cadence/mode determination, findings presentation, user review, promotion) exactly as it would under direct invocation:

• `knowledge` → Use the `Skill` tool to invoke `audit-knowledge` (with any passthrough args).
• `config` → Use the `Skill` tool to invoke `audit-config` (with any passthrough args).
• `style` → Use the `Skill` tool to invoke `audit-style` (with any passthrough args).
• `usage` → Use the `Skill` tool to invoke `audit-usage` (with any passthrough args).
• `rules` → Use the `Skill` tool to invoke `audit-rules` (with any passthrough args).
• `share` → Use the `Skill` tool to invoke `audit-share` (with any passthrough args).

`/audit`'s job ends at the handoff — it does not re-implement, intercept, or post-process what the sub-skill does. Whatever the sub-skill reports (findings, promotions, "nothing new to extract") is the final output of that leg.

Canonical forms and compatibility

**The `/audit <verb>` space forms are the canonical, advertised invocations for the whole f