review-session
Review Session
Review a single Claude Code session transcript for quality and produce actionable findings.
Prerequisites
- The
ed3d-extending-claudeplugin must be installed. - The
ed3d-session-reflectionplugin must be installed (provides theconversation-revieweragent andreduce-transcript.pyscript). - The current session's transcript path must be available (injected by the SessionStart hook). If it is not available, ask the user for the transcript path.
Invocation
The user may invoke this as:
/review-session— review the current session/review-session /path/to/transcript.jsonl— review a specific transcript
If no argument is provided, use the current session's transcript path (from the SessionStart hook context injection).
Steps
1. Determine the transcript path
If an argument was provided, use it as the transcript path. Otherwise, use the current session's transcript path from the SessionStart hook injection.
If you cannot determine the transcript path, tell the user:
I don't know the current session's transcript path.
Either provide a path: /review-session /path/to/session.jsonl
Or ensure the ed3d-session-reflection SessionStart hook is active.
2. Reduce the transcript
Run the reduction script to produce a token-efficient version:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/reduce-transcript.py" "<transcript_path>" "/tmp/session-review/reduced.txt"
Tell the user you're reducing the transcript for analysis.
3. Dispatch the reviewer
Create a temporary output path for findings:
/tmp/session-review/findings.md
Dispatch the conversation-reviewer agent with:
Transcript path: /tmp/session-review/reduced.txt Write your findings to: /tmp/session-review/findings.md
Read the transcript, analyze it, and write your findings following your output format.
4. Present findings
Once the reviewer completes, read /tmp/session-review/findings.md and present the findings to the user.
Present the full findings — do not summarize or truncate. The reviewer has already calibrated the length to be proportional to what's interesting.
More from ed3dai/ed3d-plugins
playwright-debugging
Use when Playwright scripts fail, tests are flaky, selectors stop working, or timeouts occur - provides systematic debugging approach for browser automation issues
26researching-on-the-internet
Use when planning features and need current API docs, library patterns, or external knowledge; when testing hypotheses about technology choices or claims; when verifying assumptions before design decisions - gathers well-sourced, current information from the internet to inform technical decisions
23using-generic-agents
Use to decide what kind of generic agent you should use
18coding-effectively
ALWAYS use this skill when writing or refactoring code. Includes context-dependent sub-skills to empower different coding styles across languages and runtimes.
17requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches code-reviewer subagent, handles retries and timeouts, manages review-fix loop until zero issues
14maintaining-project-context
Use when completing development phases or branches to identify and update CLAUDE.md or AGENTS.md files that may have become stale - analyzes what changed, determines affected contracts and documentation, and coordinates updates
13