solo-audit

# /audit Audit the knowledge base for quality issues: missing frontmatter, broken links, tag inconsistencies, orphaned files, and coverage gaps. Works on any markdown-heavy project. ## Steps 1. **Parse focus area** from `$ARGUMENTS` (optional). If provided, focus on that area (e.g., "tags", "frontmatter", "links"). If empty, run full audit. 2. **Find all markdown files:** Use Glob to find all .md files, excluding common non-content directories: `.venv/`, `node_modules/`, `.git/`, `archive/`, `.archive_old/`. 3. **Frontmatter audit:** First, scan a sample of existing files (first 10-20) to detect the frontmatter schema in use (which fields exist, what values are common for `type` and `status`). Then for each markdown file, check: - Has YAML frontmatter (starts with `---` and has closing `---`) - Core fields present: `title`, `tags` (and any other fields consistently used across the KB) - `type` and `status` values (if used) are consistent with the detected schema - `tags` is a non-empty list Track files missing frontmatter and files with incomplete/invalid frontmatter. 4. **Link check:** Look for broken internal links: - Grep for markdown links `\[.*\]\(.*\.md\)` and verify each target file exists - If a link-checking script exists in the project (e.g., `scripts/check_links.py`), run it as well 5. **Tag consistency audit:** Use Grep to find all `tags:` sections across .md files. Look for: - Near-duplicate tags (e.g., "ai" vs "AI" vs "artificial-i...