axiom health check

Security Community

Skill notes

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.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Security
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@CharlesWiltgen · MIT
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
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:

02
Phase 1: Detect Which Auditors to Run

Gather the Swift-file universe according to Phase 0 mode: Full audit: Glob `/*.swift`. Diff-scoped audit: Use the file list from the `DIFF SCOPE` block. Do NOT Glob — the launcher already enumerated the relevant files. Then use Grep over that file set to detect framework signals.

03
Phase 2: Launch Auditors in Parallel

Dispatch one Agent call per auditor selected in Phase 1. Do not merge auditors, skip them, or run their scans inline. N selected → N Agent calls in parallel. Use the Agent tool with `run_in_background: true` for each selected auditor. Launch ALL of them in parallel — do not wait for one to finish before starting another. Today's date tag for filenames: use ISO format `YYYY-MM-DD`. Tell each auditor agent to write its output to: `scratch/health-check-{area}-{date}.md`

04
Phase 3: Collect and Deduplicate

After all auditors complete: Use TaskOutput to collect the summary from each background agent launched in Phase 2. Wait for all agents to return before proceeding. Read each `scratch/health-check-*-{date}.md` file Parse findings — look for file:line references and severity levels Identify duplicate file:line references across multiple auditor reports

05
Phase 4: Generate Unified Report

Write to `scratch/health-check-{date}.md` (full audit) or `scratch/health-check-diff-{date}.md` (diff-scoped) with:

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.