View current session info or search conversation history. Use when debugging sessions, reviewing activity, finding past discussions, or summarizing recent work.
Searches conversation history and analyzes session data for debugging and review.
npx claudepluginhub bendrucker/claudeThis skill is limited to using the following tools:
README.mdcli/concurrent.tscli/date.tscli/debug.tscli/errors.tscli/files.tscli/format.tscli/index.tscli/parse.tscli/query.tscli/score.tscli/search.test.tscli/stats.tscli/types.tsfixtures/sessions/-Users-test-project-feature/feature.jsonlfixtures/sessions/-Users-test-project/basic.jsonlfixtures/sessions/-Users-test-project/malformed.jsonlfixtures/sessions/-Users-test-project/multiple.jsonlfixtures/sessions/-Users-test-project/summary.jsonlfixtures/sessions/-Users-test-project/tools.jsonlSearch and analyze Claude Code conversation history.
Current Session ID: ${CLAUDE_SESSION_ID}
CLI=${CLAUDE_PLUGIN_ROOT}/skills/session/cli
List recent sessions with summaries.
# Today's sessions
bun $CLI digest --after today
# View the current session
bun $CLI digest --session $CLAUDE_SESSION_ID
# JSON output for piping
bun $CLI digest --after today --format json | jq '.[].sessionId'
Search conversations by keyword.
bun $CLI search "error handling"
bun $CLI search "auth" --after yesterday
Show tool usage statistics.
bun $CLI stats --after "last week"
bun $CLI stats --sort rate # Sort by error rate
List tool errors.
bun $CLI errors --after "last week"
bun $CLI errors --type failure # Exclude user rejections
bun $CLI errors --aggregate # Group by error message
--after DATE - Filter by date (e.g., "today", "yesterday", "last week")--before DATE - Filter by date--project PATH - Filter by project path--limit N - Maximum results--format FORMAT - Output format: text (default) or json--log-level LEVEL - Telemetry output: debug (logs) or trace (logs + spans)--log-file PATH - Write traces and logs to a JSONL fileFor deeper inspection of a single session, use jq directly:
# Session file path pattern
FILE=~/.claude/projects/-Users-ben-src-project/$CLAUDE_SESSION_ID.jsonl
# List all tool uses
jq -r 'select(.type == "assistant") | .message.content[]? | select(.type == "tool_use") | .name' < "$FILE"
# Get the session summary
jq -r 'select(.type == "summary") | .summary' < "$FILE"
# Count message types
jq -r '.type' < "$FILE" | sort | uniq -c
Session logs are stored in ~/.claude/projects/<encoded-path>/<session-id>.jsonl where the encoded path replaces / with -.
Each line is a JSON object with a type field:
user - User messages (check isMeta for system messages)assistant - Claude responses with message.content[] arrayprogress - Tool execution progress and hook eventssummary - Conversation summariesYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.