This skill should be used when the user asks to "analyze session", "세션 분석", "evaluate skill execution", "스킬 실행 검증", "check session logs", "로그 분석", provides a session ID with a skill path, or wants to verify that a skill executed correctly in a past session. Post-hoc analysis of Claude Code sessions

Session Analyzer Skill Post hoc analysis tool for validating Claude Code session behavior against SKILL.md specifications. Purpose Analyze completed sessions to verify: 1. Expected vs Actual Behavior Did the skill follow SKILL.md workflow? 2. Component Invocations Were SubAgents, Hooks, and Tools called correctly? 3. Artifacts Were expected files created/deleted? 4. Bug Detection Any unexpected errors or deviations? Input Requirements Parameter Required Description sessionId YES UUID of the session to analyze targetSkill YES Path to SKILL.md to validate against additionalRequirements NO Extra validation criteria Phase 1: Locate Session Files Step 1.1: Find Session Files Session files are located in ~/.claude/ : Use script to locate files: Step 1.2: Verify Files Exist Check all required files exist before proceeding. If debug log is missing, analysis will be limited. Phase 2: Parse Target SKILL.md Step 2.1: Extract Expected Components Read the target SKILL.md and identify: From YAML Frontmatter: hooks.PreToolUse Expected PreToolUse hooks and matchers hooks.PostToolUse Expected PostToolUse hooks hooks.Stop Expected Stop hooks hooks.SubagentStop Expected SubagentStop hooks allowed tools Tools the skill is allowed to use From Markdown Body: SubAgents mentioned ( Task(subagent type="...") ) Skills called ( Skill("...") ) Artifacts created ( .dev flow/drafts/ , .dev flow/plans/ , etc.) Workflow steps and conditions Step 2.2: Build Expected Behavior Checklist Create checklist from SKILL.md analysis: Phase 3: Analyze Debug Log The debug log ( ~/.claude/debug/{sessionId}.txt ) contains detailed execution traces. Step 3.1: Extract SubAgent Calls Search patterns: Use script: Step 3.2: Extract Hook Events Search patterns: Use script: Step 3.3: Extract Tool Calls Search patterns: Step 3.4: Extract Hook Results For prompt based hooks, find the model response: Phase 4: Verify Artifacts Step 4.1: Check File Creation For each expected artifact: 1. Search debug log for FileHistory: Tracked file modification for {path} 2. Search for File {path} written atomically 3. Verify current filesystem state Step 4.2: Check File Deletion For files that should be deleted: 1. Search for rm commands in Bash calls 2. Verify file no longer exists on filesystem Phase 5: Compare Expected vs Actual Step 5.1: Build Comparison Table Step 5.2: Identify Deviations Flag any mismatches: Missing component calls Wrong order of operations Hook failures Missing artifacts Unexpected errors Phase 6: Generate Report Report Template Scripts Reference Script Purpose find session files.sh Locate all files for a session ID extract subagent calls.sh Parse subagent invocations from debug log extract hook events.sh Parse hook events from debug log Usage Example Additional Resources Reference Files references/analysis patterns.md Detailed grep patterns for log analysis references/common issues.md Known issues and troubleshooting Scripts scripts/find session files.sh Session file locator scripts/extract subagent calls.sh SubAgent call extractor scripts/extract hook events.sh Hook event extractor

session-analyzer