session-insightslisted

# Session Insights Analyze the current project's Claude Code usage patterns and generate actionable recommendations. ## Step 1: Gather session data Collect data from available sources in the current project: 1. **Session metrics** — `~/.claude/metrics/{project-slug}/*.json` (structured JSON from session-report hook) 2. **CLAUDE_ERRORS.md** — error frequency by Area and Type 3. **Git log** — files most frequently modified in commits mentioning "fix", "bug", "error" 4. **.claude/agent-memory/** — learnings accumulated by agents 5. **Registry history** — audit score trend from `$DOTFORGE_DIR/registry/projects.yml` If a source doesn't exist, skip it and note as "unavailable". ### Retroactive Analysis (no session metrics yet) When `~/.claude/metrics/{project-slug}/` is empty or doesn't exist, reconstruct a pseudo-historical picture: 1. **CLAUDE_ERRORS.md** → parse dates and group errors by week/month to show trends 2. **Git log** → `git log --name-only --since="60 days ago"` to identify: - Hot files (most frequently changed) - Fix frequency (`git log --grep="fix" --oneline | wc -l`) - Commit cadence by week 3. **Registry history** → score progression over time 4. **Rule glob coverage** → cross-reference `git log --name-only` against `.claude/rules/*.md` globs to estimate historical rule coverage Mark all retroactive data clearly as: ``` ⚠ Inferred from git history — no session metrics available yet. Session metrics will accumulate automatically after /forge sy