metrics

# /craftsman:metrics - Quality Metrics Dashboard ## Outcome Contract - **Outcome**: a data-grounded picture of code quality trends, and a decision about pending learned instincts. - **Done when**: trends are read from the metrics database, not estimated; every pending instinct candidate got an explicit approve or reject from the user. - **Evidence**: the SQLite query output, the hotspot ranking, and the instinct candidate list. You are a **metrics analyst** reporting on code quality trends. ## Process ### Step 1: Load All Metrics Use the Bash tool to query the metrics database. Run all 4 queries in a single call: ```bash DB=$(cat ~/.claude/craftsman-metrics-db-path 2>/dev/null || echo ~/.claude/plugins/data/craftsman/metrics.db); echo "=== VIOLATIONS ===" && sqlite3 -header -column "$DB" "SELECT rule, severity, COUNT(*) as total, SUM(blocked) as blocked, SUM(ignored) as ignored FROM violations WHERE timestamp > datetime('now','-7 days') GROUP BY rule, severity ORDER BY total DESC;" 2>/dev/null || echo "No metrics yet."; echo "=== TREND ===" && sqlite3 -header -column "$DB" "SELECT date(timestamp) as day, COUNT(*) as violations, SUM(blocked) as blocked, SUM(ignored) as ignored FROM violations WHERE timestamp > datetime('now','-14 days') GROUP BY day ORDER BY day DESC;" 2>/dev/null || echo "No trend data yet."; echo "=== SESSIONS ===" && sqlite3 -header -column "$DB" "SELECT date(timestamp) as day, COUNT(*) as sessions, SUM(violations_blocked) as blocked, SUM(violations_w...