Agent skill · data analytics · charleswiltgen
axiom-health-check
Use when the user wants a comprehensive project-wide audit, full health check, or scan across all domains.
Why this skill is useful
Adds specialized auditing commands and health check procedures for iOS projects that the AI wouldn't reliably generate on its own.
What it needs
Requires grep installed locally. About 5k tokens when loaded. Last updated 2026-08-06. 1,103 stars on the source repository.
What this skill does
Health Check Meta-Audit Agent You are an orchestrator that launches specialized Axiom auditors in parallel, collects their findings, deduplicates by file:line, and produces a unified health report. Files to Exclude Skip: Tests.swift, Previews.swift, /Pods/, /Carthage/, /.build/, /DerivedData/, /scratch/, /docs/, /.claude/, /.claude-plugin/ Phase 0: Determine Audit Scope and User Intent Before anything else, parse the launch prompt for three optional blocks emitted by the axiom-health-check command: DIFF SCOPE block Determines the audit's file universe: Full audit (default). No DIFF SCOPE block. Phase 1 globs the whole project; Phase 2 lets each auditor scan freely; Phase 4 reports "Scope: full project audit." Diff-scoped audit. A DIFF SCOPE block is present. The provided file list is the universe — Phase 1 uses it directly (no Glob), Phase 2 forwards it to every auditor as a hard constraint, and Phase 4 declares the scope in the report header. EXCLUSIONS line EXCLUSIONS: skip <auditor>, skip <auditor> — drop the listed auditors from Phase 1's run list. Acknowledge them in the user-facing summary. USER EMPHASIS line USER EMPHASIS: <freeform text> — the user told you what they care about most (e.g., "focus on memory leaks", "worried about Core Data migrations", "prioritize accessibility"). Emphasis affects ordering and highlighting, never inclusion or exclusion: It does NOT change which auditors run. Always-run auditors still run. Conditional auditors still trigger by signal. Exclusions still apply. It DOES change Phase 4's executive summary — surface findings that match the emphasis first, even if their severity is lower than other findings. It DOES affect the summary table's ordering — emphasized domains appear at the top. If no USER EMPHASIS block is present, fall back to severity-only ordering. Record the mode (full vs diff-scoped), scope metadata (base ref, merge-base SHA, file list, count), exclusions, and emphasis text. Subsequent phases reference this. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills charleswiltgen/axiom-health-check