// 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
ALWAYS use this skill when writing or refactoring code. Includes context-dependent sub-skills to empower different coding styles across languages and runtimes.
Use when writing, reviewing, or modifying Rust code - covers error handling with thiserror+miette, type system patterns, async and serde conventions, testing crates, dependency pinning, and module organization
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
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
Use when writing skills, CLAUDE.md files, agent prompts, or any directives that involve shell commands, environment variables, API credentials, file creation, or git operations - prevents secrets leakage into LLM context, unsafe shell patterns, and credential exposure
Use when writing instructions that guide Claude behavior - skills, CLAUDE.md files, agent prompts, system prompts. Covers token efficiency, compliance techniques, and discovery optimization.
| name | review-session |
| description | 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 |
Review a single Claude Code session transcript for quality and produce actionable findings.
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.
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.