tiered-audit

# Tiered Audit ## Table of Contents - [When to Use](#when-to-use) - [When NOT to Use](#when-not-to-use) - [Tier 1: Git History Audit](#tier-1-git-history-audit) - [Tier 2: Targeted Area Audit](#tier-2-targeted-area-audit) - [Tier 3: Full Codebase Audit](#tier-3-full-codebase-audit) - [Output Contract](#output-contract) ## When To Use - Auditing codebase quality, patterns, or problems - Reviewing what changed on a branch before merge - Investigating areas of instability or churn - Pre-PR quality assessment ## When NOT to Use - Reviewing a specific file (use pensive:code-reviewer) - Architecture-only review (use pensive:architecture-review) - Single-commit review (use imbue:diff-analysis) ## Tier 1: Git History Audit **Always runs first.** Analyzes git log, diff stats, and blame to identify areas of concern without reading any source files. ### What Tier 1 Analyzes Run these git commands for the target commit range (default: current branch vs main): ```bash # 1. Churn hotspots: files changed most often git log --format="" --name-only {base}..HEAD \ | sort | uniq -c | sort -rn | head -20 # 2. Diff stats: size of changes per file git diff --stat {base}..HEAD # 3. Fix-on-fix patterns: commits fixing previous commits git log --oneline {base}..HEAD \ | grep -iE "(fix|revert|patch|hotfix)" # 4. New file clusters: modules with many new files git diff --name-status {base}..HEAD \ | grep "^A" | cut -f2 \ | sed 's|/[^/]*$||' | sort | uniq -c | sort -rn # 5. Large c...