Diagnose Swift concurrency issues and guide Swift 6 migrations.
npx skills add https://github.com/n0an/VivaDicta --skill swift-concurrency-n0an
Please help me install this Agent Skill. Skill: swift-concurrency Source: https://github.com/n0an/VivaDicta/tree/main/.agents/skills/swift-concurrency Command: npx skills add https://github.com/n0an/VivaDicta --skill swift-concurrency-n0an
Diagnose data races, guides Swift concurrency migrations, and clarifies actor isolation and Sendable conformance for Swift 6 across codebases.
Refactor a callback-based API to async/await and apply proper actor isolation practices.
High-intent search queries and answers about installing and using this skill.
To migrate to Swift 6, you must analyze project settings and incrementally adopt async/await, implement actor isolation, and enforce Sendable conformance to eliminate data races.
The best way to refactor callback-based APIs to async/await is by applying proper actor isolation practices to safely manage state and structure asynchronous execution.
You need Sendable conformance for Swift concurrency to guarantee types are safe to pass across actor boundaries, effectively preventing data races during concurrent execution.
Yes, you can use actor isolation to fix data races in your iOS codebase by synchronizing access to mutable state and preventing concurrent modifications.
Structured concurrency applies to Swift 6 migration by enforcing hierarchical task lifecycles, ensuring async/await operations are safely scoped and preventing unstructured task leaks.
ROLLED740Define Swift 6.2 concurrency safety with explicit @concurrent offloading rules.
KKodiacIdentify and resolve Swift concurrency issues across async/await, actors, and Sendable conformance.
horizontalsystemsDiagnose data races and convert callback-based Swift code to async/await.
tranceeMigrate Swift code to Swift 6 strict concurrency by resolving Sendable and actor-isolation diagnostics.
