session-deep-dive

Featured

Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.

Code & Development 507 stars 35 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
90
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Session Deep Dive (Tier 2) Qualitative analysis of high-signal sessions identified by `/session-scan`. Spawns subagents with pre-computed metrics context for focused analysis. ## Requirements Requires **ccrider MCP**. If not available: > ccrider MCP is required. See: <https://github.com/neilberkman/ccrider> ## Usage ``` /session-deep-dive ffa155ee-ed8a-492c-8797-878fcbec4d9e /session-deep-dive --last # Most recent Tier 2 eligible /session-deep-dive --from-scan # All Tier 2 eligible from last scan /session-deep-dive --from-scan --compare .claude/UPDATED_PLUGIN_REPORT_160_SESSIONS.md ``` ## Pipeline ### Step 1: Resolve Target Sessions From `$ARGUMENTS`: - **Session ID**: Single session to analyze - **`--last`**: Most recent Tier 2 eligible session from metrics.jsonl - **`--from-scan`**: All sessions where `tier2_eligible: true` AND `tier2_completed: false` in `.claude/session-metrics/metrics.jsonl` - **`--compare REPORT.md`**: Previous report to compare against (default: most recent `.claude/session-analysis/insights-*.md`) If no metrics.jsonl exists, tell the user: > No metrics found. Run `/session-scan` first to discover and score sessions. ### Step 2: Load Pre-computed Metrics For each target session, read its entry from `metrics.jsonl`. Format the metrics as a context block for subagent prompts: ``` ## Pre-computed Metrics (from /session-scan) - Friction: 0.42 (retry_loops: 1, user_corrections: 3, approach_changes: 2) -...

Details

Author
oliver-kriska
Repository
oliver-kriska/claude-elixir-phoenix
Created
5 months ago
Last Updated
yesterday
Language
Python
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Featured

session-scan

Compute metrics for Claude Code sessions. Discovers via ccrider, filters trivial, computes friction/opportunity/fingerprint scores. Use for broad session triage.

507 Updated yesterday
oliver-kriska
AI & Automation Solid

session-debug

Debug a specific session by inspecting its full event chain (PreToolUse, PostToolUse, Stop, SubagentStop, Compaction, APIError, TurnDuration, Notification events), agent hierarchy (recursive parent/child tree with subagent_type and depth), token usage with compaction baselines, workflow intelligence data (orchestration DAG, error propagation by depth), and session metadata (thinking_blocks, turn_count, total_turn_duration_ms).

854 Updated today
hoangsonww
AI & Automation Listed

session-analysis

Use when the user wants a judgment-level read on whether a Claude Code session stayed on task — did the agent do what was originally asked, and what did it acknowledge skipping. This is the interpretive (LLM) complement to the deterministic `session-audit` CLI: 1a extracts ask-vs-done for free; this skill adds the `Variance` and `What was NOT done` judgment that a parser can't compute, then persists a combined record for drift analysis. Cost: ~1-3k tokens of the current session, paid only when invoked. Opt-in by design — run it selectively, not on every session. Best run in a Sonnet (or stronger) session; the judgment quality depends on it. Use `session-audit` (CLI) for the free deterministic ask/actions extract. Use `usage-analysis` for token-spend insights. Use `claude-audit` for agent/skill config overlap. Use THIS skill for "did this session drift from what I asked". Trigger phrases: "/session-analysis", "did this session stay on task", "analyze session drift", "did the agent do what I asked", "what did t

1 Updated today
glitchwerks