axiom-concurrency

Name: axiom-concurrency
Availability: InStock
Author: dengnaichen

Diagnose Swift 6 concurrency issues including data races and actor isolation violations.

34|2|Updated Mar 16, 2026

Search Tags:#performance #debugging #concurrency #swift #async-await #actors

Ready to run

npx skills add https://github.com/DengNaichen/Stet --skill axiom-concurrency

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: axiom-concurrency
Source: https://github.com/DengNaichen/Stet/tree/main/.agents/skills/axiom-concurrency
Command: npx skills add https://github.com/DengNaichen/Stet --skill axiom-concurrency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill resolves complex Swift 6 concurrency issues, including data races, actor isolation errors, and main thread blocking, which are common causes of production crashes and UI freezes.

Core Features & Use Cases

Diagnostic Workflows: Provides clear paths to resolve runtime isolation crashes like _dispatch_assert_queue_fail and _swift_task_checkIsolatedSwift.
Concurrency Patterns: Offers battle-tested patterns for async/await, TaskGroups, and actor reentrancy.
Profiling Guidance: Includes specific Instruments workflows to identify actor contention and thread pool exhaustion.
Use Case: Use this skill when your app crashes in production despite having a warning-free build, or when you need to safely migrate legacy delegate callbacks to modern Swift concurrency.

Quick Start

Invoke the concurrency auditor to perform a semantic audit of your codebase for Swift 6 concurrency readiness.

Frequently Asked Questions about axiom-concurrency

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fix Swift 6 data race crashes that happen in production but pass build warnings?▼

Swift 6 data races are resolved by auditing actor isolation boundaries and applying correct async/await patterns. This approach diagnoses runtime isolation failures and implements thread-safe actor architectures to eliminate concurrent access violations causing production crashes.

Why does my Swift app crash with _dispatch_assert_queue_fail during async tasks?▼

Your Swift app crashes with _dispatch_assert_queue_fail due to main thread blocking or actor isolation violations. Resolving this requires diagnostic workflows that check isolated Swift tasks and migrate legacy delegate callbacks to modern concurrency patterns safely.

How do I migrate legacy delegate callbacks to Swift async/await without thread exhaustion?▼

Migrating legacy delegate callbacks to Swift async/await requires applying battle-tested concurrency patterns and TaskGroups. This prevents thread pool exhaustion by ensuring proper isolation inheritance and safe actor reentrancy across your asynchronous workflows.

Can I use Instruments to profile actor contention and thread pool exhaustion in Swift?▼

Yes, you can use Instruments to profile actor contention and thread pool exhaustion in Swift. Specific profiling workflows allow you to identify performance bottlenecks and optimize async/await patterns within the Swift concurrency runtime.

What is the best way to resolve actor isolation violations when migrating to Swift 6 concurrency?▼

The best way to resolve actor isolation violations is performing a semantic audit of your codebase for Swift 6 readiness. This identifies isolation inheritance issues and provides clear diagnostic paths to fix reentrancy and runtime crashes.