axiom-audit-testing
Axiom Audit Testing systematically scans your test files and production code to surface flaky patterns, missing coverage on critical paths, and opportunities to modernize your test suite. It identifies sleep calls and shared state that cause timing failures, flags tests that require unnecessary simulator overhead, and maps which auth, payment, persistence, and networking flows lack test coverage. The agent also spots XCTestCase candidates ready for Swift Testing migration and detects ungrounded AI evaluation gates that generate false failures.
Axiom Audit Testing scans your Swift test suite to find flaky patterns, coverage gaps, and quality issues holding back your team.
AI-generated summary based on this skill's SKILL.md
Install
CharlesWiltgen/Axiom/axiom-audit-testing · repository language: Go
git clone https://github.com/CharlesWiltgen/Axiom
cp -r Axiom/axiom-codex/skills/axiom-audit-testing ~/.claude/skills/axiom-audit-testingFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What does Axiom Audit Testing do?
Axiom Audit Testing systematically scans your test files and production code to surface flaky patterns, missing coverage on critical paths, and opportunities to modernize your test suite. It identifies sleep calls and shared state that cause timing failures, flags tests that require unnecessary simulator overhead, and maps which auth, payment, persistence, and networking flows lack test coverage. The agent also spots XCTestCase candidates ready for Swift Testing migration and detects ungrounded AI evaluation gates that generate false failures.
How does Axiom Audit Testing help audit test quality Swift?
Axiom Audit Testing audits test quality by analyzing your entire test suite for flaky patterns, timing-dependent code, and shared mutable state that causes intermittent failures. It scans for sleep calls in unit tests, detects anti-patterns that reduce reliability, and generates a test health score report showing which tests are most prone to failure. The tool prioritizes the highest-impact issues so you can fix the most damaging quality problems first.
Can Axiom Audit Testing help migrate to Swift Testing?
Yes. Axiom Audit Testing identifies and fixes tests preventing Swift Testing migration by scanning for XCTestCase patterns, async test structures, and concurrency issues that block the move from XCTest to Swift Testing framework. It flags shared mutable state in tests and detects Swift 6 concurrency compliance gaps in your test code, making the migration path clearer and reducing blockers.
How does it speed up test execution time?
Axiom Audit Testing speeds up test execution by detecting tests with unnecessary simulator overhead—such as those that launch the full simulator when they could run as unit tests. It also identifies sleep calls and other timing-dependent patterns that artificially slow down your suite. By flagging these inefficiencies, you can refactor tests to run faster without sacrificing coverage.
What test coverage gaps does Axiom Audit Testing find?
Axiom Audit Testing finds untested critical paths and error handling code by mapping which auth, payment, persistence, and networking flows lack test coverage. It detects missing test coverage gaps in your codebase and identifies error paths that are never exercised, helping you prioritize test development on the flows that matter most to your app's reliability.
Is Axiom Audit Testing open source?
Yes, Axiom Audit Testing is released under the MIT license, making it free to use, modify, and distribute in both open-source and commercial projects.
SKILL.md
rendered from the published skill — quoted content, verbatim
Testing Auditor Agent
You are an expert at detecting test quality issues — both known anti-patterns AND missing/incomplete test coverage that leaves critical paths unverified.
Tool Use Is Mandatory
Run every Glob, Grep, and Read this prompt lists. Do not reason from training data instead of scanning.
- Run each Grep pattern as written; do not collapse them into one mega-regex.
- Run the Read verifications each section calls for.
- "Build a mental model" / "map the architecture" means with tool output in hand, not from memory.
Files to Scan
Test files: *Tests.swift, *Test.swift, *Spec.swift
Production files: **/*.swift (for coverage shape mapping in Phase 1)
Skip: *Previews.swift, */Pods/*, */Carthage/*, */.build/*, */DerivedData/*, */scratch/*, */docs/*, */.claude/*, */.claude-plugin/*
Phase 1: Map Test Coverage Shape
Step 1: Inventory Production and Test Code
``` Glob: */.swift (production code —
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 2 files
axiom-codex/skills/axiom-audit-testing/SKILL.md
axiom-codex/skills/axiom-audit-testing/agents/openai.yaml