plugins/ed3d-session-reflection/skills/review-session/SKILL.md
Use when the user wants to review a Claude Code session for quality — analyzes the current session (or a specified transcript path) for prompting effectiveness, agent performance, and environment gaps, producing actionable recommendations
npx skillsauth add ed3dai/ed3d-plugins-testing review-sessionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Review a single Claude Code session transcript for quality and produce actionable findings.
Do not use nested subagents. This workflow may dispatch the conversation-reviewer agent, but that agent must analyze the transcript directly and must not dispatch additional subagents.
ed3d-extending-claude plugin must be installed.ed3d-session-reflection plugin must be installed (provides the conversation-reviewer agent and reduce-transcript.py script).The user may invoke this as:
/review-session — review the current session/review-session /path/to/transcript.jsonl — review a specific transcriptIf no argument is provided, use the current session's transcript path (from the SessionStart hook context injection).
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.
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.
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. Do not dispatch or invoke any subagents. </parameter> </invoke>
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.
development
Use when the user wants to review their recent Claude Code sessions for patterns — analyzes the last N sessions (default 5) in the current project, dispatching parallel reviewers per session, then synthesizing cross-session findings
tools
Use when the user wants to export a Claude Code session transcript as a readable Markdown file — converts the current session (or a specified transcript path) into GitHub-flavored Markdown with metadata header, collapsible tool results, and thinking blocks
development
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
development
Use when planning or designing features and need to understand current codebase state, find existing patterns, or verify assumptions about what exists; when design makes assumptions about file locations, structure, or existing code that need verification - prevents hallucination by grounding plans in reality