retrolisted

# Retro ## Core Rule Report patterns from session analytics, not speculation. Distinguish process improvements from one-time mistakes. ## When to Use Invoke with `/retro` when: - End of a work sprint or week - Want to understand development velocity and patterns - Team standup or retrospective meeting prep - Assessing productivity trends over time - After a difficult period to understand what went wrong ## Process ### Phase 1: Session Detection Analyze git history to identify work sessions: 1. **Read commit log** — `git log --all --format='%H %aI %an %s' --since='1 week ago'` 2. **Detect sessions** by grouping commits with <45 min gaps between them 3. **Classify sessions**: - **Deep** (50+ min) — sustained focused work - **Medium** (20-50 min) — moderate work blocks - **Micro** (<20 min) — quick fixes, reviews, hotfixes 4. **Per author** if multiple contributors ### Phase 2: Metrics Calculate development metrics: **Volume** - Lines added / removed / net (from `git diff --stat`) - Files changed - Commits count - PRs merged (via `gh pr list --state merged` if available) **Velocity** - LOC per hour (lines changed ÷ session hours) - Commits per session - Average session duration **Patterns** - Most active files (change hotspots) - Most active directories (where work concentrates) - Commit type distribution (feat/fix/refactor/test/docs) - Time-of-day distribution (morning/afternoon/evening/night) ### Phase 3: Qualitative Analysis Review the work cont