← ClaudeAtlas

review-logslisted

Analyze Claude Code session transcripts for failure patterns and suggest fixes. Triggers "review logs", "session analysis", "failure patterns".
nielsmadan/skills · ★ 0 · Code & Development · score 75
Install: claude install-skill nielsmadan/skills
<!-- Generated from https://github.com/nielsmadan/agentic-coding — edits here are overwritten. --> # Review Logs Scan recent Claude Code session transcripts for recurring failure patterns and generate actionable recommendations. ## Usage ``` /review-logs /review-logs --days 7 /review-logs --project juggler /review-logs --days 30 --verbose ``` ## Gotchas - The `--project` filter is case-sensitive and must exactly match the directory name. `--project MyApp` vs `my-app` gives zero results with no indication of the mismatch. - In repos with read-only git policies, every blocked `git add`/`git commit` appears as a failure, dominating results and obscuring real problems. Filter known-policy denials from the output. ## Workflow ### Step 1: Parse Arguments Extract from `$ARGUMENTS`: - `--days N` — lookback window (default: 14) - `--project <name>` — filter to a specific project - `--verbose` — include problematic session IDs for manual review ### Step 2: Run Extraction Script Find the script using Glob: ``` Glob pattern: **/review-logs/scripts/extract_signals.py Path: ~/.claude ``` Run the extraction with the discovered path: ```bash python3 <discovered-path>/extract_signals.py --days <N> [--project <name>] --output /tmp/review-logs-output.json ``` ### Step 3: Read and Analyze Output Read `/tmp/review-logs-output.json` and present findings in severity order: | Priority | Category | What to Present | |----------|----------|-----------------| | Critical | High-frequency