{"enrichment":{"faq":[{"a":"axiom-analyze-test-failures helps you pinpoint flakiness sources: timing issues in async code, race conditions from parallel execution, shared mutable state, or environment misconfigurations. Start by checking whether failures are deterministic locally or only in CI. Flakiness often stems from unwaited async operations, missing @MainActor isolation in Swift 6, or test.sleep calls with insufficient duration. The skill guides you through isolating whether the problem is a code defect or a test infrastructure issue.","q":"Why are my tests flaky with axiom-analyze-test-failures?"},{"a":"axiom-analyze-test-failures addresses this common scenario by helping you identify environmental differences. CI runners often execute tests in parallel with stricter timing constraints and different resource availability. Check for race conditions in shared state, missing serialized traits on test classes, and async operations that aren't properly awaited. Compare your local test execution (serial vs. parallel) with CI settings. Symbolicate any crash logs from CI runs to reveal hidden failures masked by timing differences.","q":"Test passes locally but fails in CI\u2014how do I diagnose this?"},{"a":"axiom-analyze-test-failures guides you through detecting and resolving race conditions by analyzing parallel test patterns. Swift Testing race conditions typically arise from concurrent access to shared mutable state without proper synchronization. The skill helps you identify missing @MainActor annotations, unsafe property access across test tasks, and improper use of actor isolation. It also advises on applying the serialized trait to prevent parallel execution when tests genuinely share resources.","q":"How does axiom-analyze-test-failures handle Swift Testing race conditions?"},{"a":"axiom-analyze-test-failures identifies common flaky async patterns: missing await on async operations, insufficient test.sleep durations, unconfirmed expectations in Swift Testing, and tasks that outlive test scope. It helps you spot when async work isn't properly awaited before test completion, causing intermittent failures. The skill also flags Swift 6 concurrency violations like missing @MainActor isolation on test data and improper actor boundary crossings that cause data races.","q":"What async test patterns does axiom-analyze-test-failures identify as flaky?"},{"a":"axiom-analyze-test-failures ensures your tests comply with Swift 6's strict concurrency model. It helps identify missing @MainActor annotations on test methods and shared test data, detects unsafe actor boundary crossings, and flags data race warnings. The skill guides you through properly isolating test state, using nonisolated(unsafe) only when justified, and structuring async test code to satisfy the compiler's concurrency requirements while maintaining test reliability.","q":"How can axiom-analyze-test-failures help with Swift 6 concurrency test errors?"},{"a":"axiom-analyze-test-failures teaches you to prevent race conditions by: avoiding shared mutable state across parallel tests, applying the serialized trait when tests must run sequentially, using actors for thread-safe test data, and ensuring @MainActor isolation where needed. It helps you analyze test crashes and symbolicate logs to reveal hidden concurrency issues. The skill emphasizes proper async/await patterns, explicit test ordering when dependencies exist, and thorough verification that all async operations complete before assertions run.","q":"How do I prevent race conditions in tests using axiom-analyze-test-failures?"}],"shadow_tags":["async-debugging","ci-reliability","concurrency-safety","test-isolation","failure-diagnosis","race-condition-detection","swift-6-migration","timing-stability","crash-analysis"],"summary_rewrite":"This skill equips AI coding assistants with specialized knowledge for troubleshooting flaky tests in Swift and Apple OS environments. It helps identify whether failures stem from timing issues, resource contention, environment misconfigurations, or code defects\u2014critical for maintaining reliable CI pipelines. Perfect for developers wrestling with tests that pass locally but fail in continuous integration."},"files":[{"bytes":11592,"path":"axiom-codex/skills/axiom-analyze-test-failures/SKILL.md","sha256":"51de7f3d68ba785d289ce688fbba17b2c35aa3ed9cc460d837027145cc02ba4a","url":"https://skillfed.io/files/CharlesWiltgen/Axiom/axiom-analyze-test-failures/bf437845/SKILL.md"}],"id":"CharlesWiltgen/Axiom/axiom-analyze-test-failures","links":{"html":"https://skillfed.io/CharlesWiltgen/Axiom/axiom-analyze-test-failures","md":"https://skillfed.io/CharlesWiltgen/Axiom/axiom-analyze-test-failures.md","repo":"https://github.com/CharlesWiltgen/Axiom"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":81,"language":"Go","last_updated":"2026-07-27","license":"MIT","name":"axiom-analyze-test-failures","publisher":"CharlesWiltgen","stars":1095},"relations":{"similar":[{"id":"dpearson2699/swift-ios-skills/swift-testing"},{"id":"CharlesWiltgen/Axiom/axiom-debug-tests"},{"id":"CharlesWiltgen/Axiom/axiom-analyze-crash"},{"id":"tartinerlabs/skills/modernize-tests"},{"id":"superagents-lab/xcode27-skills/test-modernizer"},{"id":"CharlesWiltgen/Axiom/axiom-audit-concurrency"},{"id":"rshankras/claude-code-apple-skills/test-generator"},{"id":"CharlesWiltgen/Axiom/axiom-audit-testing"},{"id":"CharlesWiltgen/Axiom/axiom-analyze-triage"},{"id":"Aradotso/marketing-skills/ios-marketing-capture-automation"}]},"slug":{"owner":"CharlesWiltgen","repo":"Axiom","skill":"axiom-analyze-test-failures"},"version":"bf437845"}