forensics
Forensics Skill
Investigate failed or stuck workflows through post-mortem analysis of git history, plan files, and session artifacts. Forensics answers "what went wrong and why" -- it detects workflow-level failures that individual tool errors don't reveal.
Key distinction: A tool error is "ruff found 3 lint errors." A workflow failure is "the agent entered a fix/retry loop editing the same file 5 times and never progressed." The error-learner handles tool-level errors. Forensics handles workflow-level patterns.
Reference Loading
| Task | Load |
|---|---|
| Collecting git evidence, running git log commands, scrubbing credentials | references/evidence-collection.md |
| Identifying failure type from symptoms, causal chain analysis | references/failure-signatures.md |
| Running any of the 5 anomaly detectors, scoring confidence | references/detectors.md |
Reference Loading Table
| Signal | Load These Files | Why |
More from notque/claude-code-toolkit
generate-claudemd
Generate project-specific CLAUDE.md from repo analysis.
12fish-shell-config
Fish shell configuration and PATH management.
12pptx-generator
PPTX presentation generation with visual QA: slides, pitch decks.
12codebase-overview
Systematic codebase exploration and architecture mapping.
10image-to-video
FFmpeg-based video creation from image and audio.
9data-analysis
Decision-first data analysis with statistical rigor gates.
9