pr-retrolisted

<!-- prettier-ignore-start --> **Document Version:** 4.8 **Last Updated:** 2026-03-18 **Status:** ACTIVE <!-- prettier-ignore-end --> # PR Review Retrospective Analyze the review cycle for completed PRs via interactive finding-by-finding walkthrough. **Invocation:** `/pr-retro` (dashboard) | `/pr-retro <PR#>` (single) | `/pr-retro <PR#> --resume` (resume from state) **Routing:** "Review code" -- `/code-reviewer` | "Process feedback" -- `/pr-review` | "Process health" -- `/pr-ecosystem-audit` | "What went well/wrong" -- `/pr-retro` ## When to Use - User invokes `/pr-retro` AND the target PR is merged - Retrospective analysis of a review cycle after merge ## When NOT to Use - Active review in progress → `/pr-review` - Code quality check → `/code-reviewer` - Ecosystem audit → `/pr-ecosystem-audit` --- ## CRITICAL RULES (MUST follow) 1. **MUST produce the FULL retro** -- every mandatory section, every round. 2. **MUST present findings interactively** -- one at a time with options. 3. **MUST save state after every finding decision** -- compaction resilience. 4. **MUST include a verify command** for every accepted action item. 5. **MUST run final verification** before saving -- verify commands, sections. 6. **MUST display closure summary** listing all artifacts produced. 7. Every observation MUST have a recommended action with estimated effort. 8. Cross-PR systemic analysis is MUST for every retro. 9. Follow CLAUDE.md Section 5 anti-patterns and Section 6 coding standard