error-auditlisted

Weekly error triage skill. Runs scripts/session-health.sh --json to get error counts by category, surfaces the top-3 recurring patterns with ranked fix suggestions, and identifies actionable root causes (flag errors, write-before-read, parallel cascade failures, hook-denied patterns, etc.). When permission errors are in the top 3, runs a settings.json gap analysis inline (formerly allowed-tools-maintainer). Triggers on: error audit, what's breaking, error report, session health, what errors keep happening, why do I keep getting errors, recurring errors, tool errors this week, fix recurring errors, settings sync, allowed tools gap, tool approval friction, settings audit, add to allow-list, skills need permissions, sync tool permissions, settings.json gaps. Not for: fixing a specific one-off error (use /fix-ci).
e128/dotnet-reference · ★ 2 · Data & Documents · score 71

Install: claude install-skill e128/dotnet-reference

Surface recurring tool-error patterns and ranked fix actions. ## Step 1: Run session health scan ```bash scripts/session-health.sh --json ``` Parse the JSON output. Key fields: - `total_errors` — total tool errors in the window - `prev_total` — baseline total (0 if no baseline saved) - `total_trend` — direction symbol - `has_baseline` — whether a saved baseline exists - `categories` — array of `{ name, count, prev, delta, trend }` ## Step 2: Rank categories Sort `categories` by `count` descending. Take the top 3 (or all if fewer than 3). ## Step 3: Map categories to root causes and fixes | Category | Root cause | Fix | |-------------------|-----------------------------------------------------------------------------|-----------------------------------------------------------------------------------| | `bash-failure` | Bash tool exited non-zero (build fail, pre-commit block, hook block, rm error) | Read the full exit text; fix the underlying build/script/hook error | | `write-before-read` | Edit/Write called before Read on the same file | Always Read before Write/Edit; re-read after every format/check/build step | | `file-modified` | Formatter/hook mutated a file between Read and Edit | Re-read after every format, check, or pre-commit hook run