axiom audit testing

Engineering Community

Skill notes

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/*

Step 2: Identify Critical Production Paths

Read key production files to identify: Auth/Security: login, token management, keychain access, biometric auth Payments/IAP: StoreKit, purchase flows, receipt validation Data persistence: SwiftData/CoreData models, migrations, save/load operations Networking: API clients, request building, response parsing, error handling

Step 3: Cross-Reference

Match production modules/directories against test files: Which production modules have corresponding test files? Which have NO test files at all? Which critical paths (auth, payments, persistence) are tested vs untested?

Output

Write a brief Coverage Shape Map (8-12 lines) summarizing: Total production modules vs modules with tests Which critical paths are tested Which critical paths are untested Test framework split (XCTest vs Swift Testing)

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
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 1: Map Test Coverage Shape

Phase 1: Map Test Coverage Shape

02
Step 1: Inventory Production and Test Code

Step 1: Inventory Production and Test Code

03
Step 2: Identify Critical Production Paths

Read key production files to identify: Auth/Security: login, token management, keychain access, biometric auth Payments/IAP: StoreKit, purchase flows, receipt validation Data persistence: SwiftData/CoreData models, migrations, save/load operations Networking: API clients, request building, response parsing, error handling

04
Step 3: Cross-Reference

Match production modules/directories against test files: Which production modules have corresponding test files? Which have NO test files at all? Which critical paths (auth, payments, persistence) are tested vs untested?

05
Phase 2: Detect Known Anti-Patterns

Run all 5 existing detection categories. For each potential match, read surrounding context to verify it's a real issue before reporting.

06
Phase 3: Reason About Test Completeness

Using the Coverage Shape Map from Phase 1 and your domain knowledge, check for what's *untested* — not just what's wrong with existing tests. Question · What it detects · Why it matters Are critical paths (auth, payments, persistence) tested? · Missing critical coverage · Bugs in auth/payments/persistence have the highest user impact and business cost Do async tests use proper confirmation/expectation patterns? · Unreliable async tests · Async tests without proper waiting are inherently flaky

07
Phase 4: Cross-Reference Findings

Bump severity for these combinations: Finding A · + Finding B · = Compound · Severity No tests for auth module · Auth uses @MainActor + async · Untested concurrency in security-critical code · CRITICAL Missing error path tests · `try!` in production code · Crash on unhandled error · CRITICAL Test uses sleep() · Tests auth flow · Flaky test on critical path · CRITICAL

08
Phase 5: Test Health Score

Scoring: WELL TESTED: All critical paths tested, <3 flaky patterns, >70% module coverage, error paths covered GAPS: Most critical paths tested, some flaky patterns or missing error coverage, or 40-70% module coverage UNDERTESTED: Critical paths untested, or >5 flaky patterns, or <40% module coverage

Discussion

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