/audit — Four-Cs Score

Read-only weekly audit. Adapted from AIS-OS. Pairs with /level-up (the action loop).

When to use

• The user runs /audit
• Weekly Friday cadence (see docs/CADENCE.md)
• Before planning a quarter — establish a baseline
• After a major change to the OS — measure drift

When NOT to use

• Daily — too noisy, the trend disappears
• Mid-task — audit is reflective, not action-driving
• For deep code review — that's /audit-deep. This is OS-level audit, not codebase audit.

Inputs

• Current state of context/, connections.md, skills/, commands/, agents/, recipes/, decisions/log.md, ~/.claude/usage.jsonl (if exists)
• Optional flag --no-save: print the report without writing to docs/audits/