audit

audit — the rules this repo wrote down for itself

A linter enforces what every project agrees on. This checks what only this project agreed on, declared as .claude/audit-rules/*.md. A rule with no file behind it is not a rule; if the directory is empty, say so rather than inventing conventions.

How It Works

1. Check for rules: Look for .claude/audit-rules/*.md files
2. If no rules exist: Suggest bootstrapping with common patterns
3. If rules exist: Validate each rule against the codebase

Rule File Format

Each .claude/audit-rules/[name].md defines:

• Pattern: What to check (regex, file pattern, or description)
• Expected: What should be true
• Severity: critical / warning / info

Common starting rules

Nothing here runs on its own. These are what to propose when .claude/audit-rules/ is empty (step 2), and each one becomes a rule only once it is written as a file:

• No hardcoded secrets (API keys, passwords, tokens)
• No console.log in production code (unless a logging library wraps it)
• No TODO/FIXME in the code being committed

Managing rules

There is no audit command to run. A rule is a file, so adding one means writing .claude/audit-rules/<name>.md, listing them means reading that directory, and removing one means deleting the file.

Output Format

## Audit Results

✅ Passed: [N] rules
⚠️ Warnings: [N]
❌ Violations: [N]

[For each violation:]
❌ [rule name] - [severity]
   [file:line] [what's wrong]
   Fix: [suggestion]