session-analyzer

Session validation compares session logs and artifact lifecycles against SKILL.md frontmatter to identify deviations and generate a structured audit trail. It checks subagent invocations, hook outcomes, and artifact drafts to ensure observed flow matches defined specifications.

Post-hoc verification of Claude Code sessions quantifies how closely a completed session conforms to a target SKILL.md, surfacing deviations across subagents, hooks, and artifacts. You need it for QA, compliance checks, or post-mortem analysis to ensure reproducible behavior.

Yes, you can analyze hook outcomes and subagent invocations from session logs to verify correct behavior. The analyzer relies on session logs, SKILL.md frontmatter, and configured artifact paths to evaluate whether the observed flow aligns with the defined workflow.

Generate a reproducible audit trail by analyzing completed session logs against target SKILL.md frontmatter and configured artifact paths. The process surfaces deviations in subagent usage, hook outcomes, and artifact drafts, producing a structured verification report for compliance.

No, the session analyzer has no external dependencies or API keys. It operates using session logs, the target SKILL.md frontmatter, and configured artifact paths to produce its structured verification report.

Session log verification is limited to post-hoc analysis of completed runs, meaning it surfaces deviations after execution rather than preventing them in real-time. It relies entirely on the accuracy of configured artifact paths and SKILL.md frontmatter to validate subagent and hook behavior.