← ClaudeAtlas

retrospectlisted

**Bare-slash canonical (Claude Code).** `/retrospect` resolves to this skill when both aria-knowledge and aria-cowork are loaded in the same session. RUNTIME GATE: if invoked from a non-Code runtime (no Bash tool available, e.g., Claude Cowork), the Runtime Gate section surfaces a notification suggesting `/aria-cowork:retrospect` and requires explicit user confirmation before proceeding — even in `auto` mode (ADR-094 §Part 3). Run a structured retrospective on a shipped commit range, release, deployment, PR, commit, or session. Per-fix validation enforcement, active evidence-sourcing pass (autonomous lookups + targeted user-asks for anything that could become objective), simpler-alternative discipline, re-diagnosis, action verdicts, and a growing failure-mode pattern library. Triggers: '/retrospect' (auto-range), '/retrospect commit <hash>', '/retrospect range <ref1>..<ref2>', '/retrospect pr <num>', '/retrospect session', '/retrospect release', '/retrospect deployment'. Backward-compat flags (--range, --pr,
mikeprasad/aria-knowledge · ★ 12 · AI & Automation · score 66
Install: claude install-skill mikeprasad/aria-knowledge
# /retrospect — Release retrospective with validation enforcement Run a structured retrospective on a shipped commit range (or single commit, or current session). Produces a 10-section markdown report with per-fix verdicts, validation status, action recommendations, and re-diagnosis when fixes failed. Writes findings to `knowledge/logs/retrospect/` and runs aria's standard intake. Source spec: `docs/specs/2026-05-03-retrospect-skill-design.md`. ## Runtime Gate (per ADR-094) **Before "When to use":** Check that `Bash` is available. If `Bash` is NOT available (e.g., Cowork), surface: > ⚠️ **Runtime mismatch — you invoked aria-knowledge's `/retrospect` from a non-Code runtime.** > > This variant runs `git log`, `git diff`, `gh pr view` directly via Bash for commit/range/pr/deployment scopes. For the Cowork-native variant (prompts user-paste for git output; session/decision scopes work unmodified), use `/aria-cowork:retrospect`. > > Proceed with the aria-knowledge variant anyway? (`y` / `n`) Wait for `y` / `yes`. **Gate applies even in `auto`** (ADR-094 §Part 3). If `Bash` is available, proceed to "When to use". ## When to use - After a release ships and the bug is partially or fully unresolved - When the user reports a regression and a recent change set could be the cause - Before proposing another fix to a bug that's already been "fixed" once - As a soft-suggested response to user pushback ("review what you did," "are these changes necessary") ## Step 0: Inputs & Mode D