retrospective-walklisted

Walk a human or agent through a diff, worktree, commit range, gateway job, or episode reference as a structured retrospective. Use after implement-review-fix or multi-LLM review cycles, when reviewing prior jobs or uncommitted work, or when durable evidence is needed for what changed, why it changed, who/when contributed, and captured human or model comments.
verivus-oss/llm-cli-gateway · ★ 15 · AI & Automation · score 80

Install: claude install-skill verivus-oss/llm-cli-gateway

# Retrospective Walk Guide a change review as a narrative with evidence. Prefer this when the user needs the story of a change set, not just hunk-level inspection. ## Inputs Accept these fields when the user supplies them, and infer conservative defaults when they do not: ```json { "scope": "diff | commit-range | worktree | job-id | episode-ref", "target": "diff text, HEAD~5..HEAD, path, job id, or episode reference", "mode": "guided | agent-driven | summary-only", "capture_comments": true, "models_for_why": [], "include_prior_evidence": true } ``` Default `mode` to `guided` for a human in the loop, `agent-driven` for automated review, and `summary-only` only when explicitly requested or when interaction is not possible. Default `capture_comments` to true. ## Scope Resolution Resolve the target into immutable evidence before analysis: - `diff`: use the supplied diff text. If the target is empty, capture `git diff --no-ext-diff` and `git diff --cached --no-ext-diff`. - `commit-range`: capture `git diff --stat <range>`, `git diff --name-status <range>`, and per-commit metadata from `git log --format=fuller <range>`. - `worktree`: capture status, dirty file list, staged diff, and unstaged diff. Do not stash, reset, or mutate the target worktree. If deeper model/tool analysis may write files, create a disposable isolated worktree or analyze a read-only evidence packet instead. - `job-id`: fetch `llm_job_status` and `llm_job_result`; include `cli`, `c