Agent skill

review-session

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

Stars 170
Forks 21

Install this agent skill to your Project

npx add-skill https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-session-reflection/skills/review-session

SKILL.md

Review Session

Review a single Claude Code session transcript for quality and produce actionable findings.

Prerequisites

  • The ed3d-extending-claude plugin must be installed.
  • The ed3d-session-reflection plugin must be installed (provides the conversation-reviewer agent and reduce-transcript.py script).
  • 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:

bash
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.

Expand your agent's capabilities with these related and highly-rated skills.

ed3dai/ed3d-plugins

doing-a-simple-two-stage-fanout

Use when analyzing a large corpus of text, code, or data that exceeds a single agent's effective context - orchestrates parallel Worker subagents, Critic review subagents, and a final Summarizer subagent with task tracking and failure recovery

170 21
Explore
ed3dai/ed3d-plugins

using-generic-agents

Use to decide what kind of generic agent you should use

170 21
Explore
ed3dai/ed3d-plugins

investigating-a-codebase

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

170 21
Explore
ed3dai/ed3d-plugins

researching-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

170 21
Explore
ed3dai/ed3d-plugins

creating-an-agent

Use when creating specialized subagents for Claude Code plugins or the Task tool - covers description writing for auto-delegation, tool selection, prompt structure, and testing agents

170 21
Explore
ed3dai/ed3d-plugins

maintaining-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

170 21
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results