Stats
Actions
Tags
From retrolens
Analyze one or more sessions: drill from overview → turns → tool calls, map phases, and produce an analysis artifact.
How this command is triggered — by the user, by Claude, or both
Slash command
/retrolens:analyzeThe summary Claude sees in its command listing — used to decide when to auto-load this command
# retrolens:analyze Command Analyze one or more sessions: drill from overview → turns → tool calls, map phases, and produce an analysis artifact. > **Full skill reference**: Read `./SKILL.md` → Workflow C for the detailed drill-down method. ## Prerequisites Run `/retrolens:connect` first to connect to a log directory. ## Usage ## Arguments - `<session-id>` - A session ID/prefix, `latest`, or omit to choose interactively ## Options - `--out <file>` - Write analysis to a file (recommended) - `--turns <range>` - Limit scope (e.g., `1-10`) - `--json` - Emit structured summary ## Wha...
Analyze one or more sessions: drill from overview → turns → tool calls, map phases, and produce an analysis artifact.
Full skill reference: Read
./SKILL.md→ Workflow C for the detailed drill-down method.
Run /retrolens:connect first to connect to a log directory.
/retrolens:analyze [<session-id>] [--out <file>] [--turns <range>] [--json]
<session-id> - A session ID/prefix, latest, or omit to choose interactively--out <file> - Write analysis to a file (recommended)--turns <range> - Limit scope (e.g., 1-10)--json - Emit structured summaryIf no <session-id> is provided, list available sessions and ask:
retrolens ls --json
Found N sessions. Which would you like to analyze?
# Date Turns Title/Preview 1 2026-04-10 23 "Fix CI build errors..." 2 2026-04-09 8 "Add custom reader..." 3 2026-04-08 45 "Refactor plugin structure..." Enter a number, session ID prefix, or
allto compare multiple sessions.
retrolens read <ID> --json # overview + turn summaries
retrolens read <ID> --turn N --json # full turn detail
retrolens read <ID> -t N --tool M # specific tool call
retrolens read <ID> --turns 1-5 --json # range of turns
retrolens read <ID> --diff 1,5 --json # compare two turns
Identify workflow stages by tool usage patterns:
| Phase | Dominant Tools |
|---|---|
| Research | read_file, semantic_search, grep_search, list_dir |
| Planning | Discussion turns, vscode_askQuestions |
| Implementation | create_file, replace_string_in_file |
| Testing | run_in_terminal with test/build commands |
| Iteration | Repeated edits after errors or user corrections |
Write to --out file (or present inline) with:
For sessions >10 turns, use sub-agents to process turn ranges in parallel.
Analysis complete. What would you like to do next?
/retrolens:reflect— Extract reusable lessons and agent directives from this analysis/retrolens:analyze <another-id>— Analyze another session- Compare with another session (provide two IDs)
npx claudepluginhub joelyyoung/retrolens --plugin retrolens/analyzeAnalyzes project code across quality, security, performance, and architecture domains, producing severity-rated findings, actionable recommendations, metrics, and reports.
/analyzeAnalyzes repository code health via complexity metrics, git churn, and test coverage. Generates report with overview, critical issues, warnings, recommendations.
/analyzeGuides through an interactive analysis of marketing campaign performance, collecting scope, period, type, and metrics focus to produce insights and recommendations.
/analyzeScans codebase for features, components, APIs, and models; interviews user for business context; generates and saves product inventory and architecture reports to .pm/.
/analyzeAnalyzes Rails codebase or directory for layered architecture adherence, mapping layers, assessing services, detecting model violations, god objects, and abstraction opportunities.
/analyzeAnalyzes a WebGPU Inspector capture for performance and correctness issues, producing a prioritized list of findings with severity, explanation, and concrete fixes.