swift-concurrency

Diagnose data races, migrate to async/await, and resolve Swift 6 concurrency issues with structured guidance. Before proposing a fix: Project settings that change concurrency behavior: If any of these are unknown, ask the developer to confirm them before giving migration-sensitive guidance. Do not guess. Guardrails: Use Quick Fix Mode when all of these are true: Skip Quick Fix Mode when any of these are true: Prefer changes that preserve behavior while satisfying data-race safety: Network request with UI update Processing array items in parallel Key changes in Swift 6: Apply this cycle for each migration change: If a fix introduces new warnings, resolve them before continuing. Never batch multiple unrelated fixes — keep commits small and reviewable. For detailed migration steps, see references/migration.md . Open the smallest reference that matches the question: When changing concurrency code: Note : This skill is based on the comprehensive Swift Concurrency Course by Antoine van der Lee. - Analyzes project settings (language mode, strict concurrency level, default isolation) before proposing fixes to ensure recommendations match your build configuration - Covers all major concurrency diagnostics: main actor isolation, actor conformance, Sendable violations, and SwiftLint warnings with smallest-safe-fix strategies - Provides Quick Fix Mode for localized, single-file issues and...