swift-concurrency-pro
Reviews Swift code for concurrency correctness, modern API usage, and common async/await pitfalls. Use when reading, writing, or reviewing Swift concurrency code.
Install
With your agent
Install OMGSkills skill "twostraws/swift-concurrency-agent-skill:swift-concurrency-pro" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/twostraws/Swift-Concurrency-Agent-Skill /tmp/Swift-Concurrency-Agent-Skill && ln -s /tmp/Swift-Concurrency-Agent-Skill/swift-concurrency-pro ~/.claude/skills/swift-concurrency-proFrom README
Core Instructions Target Swift 6.2 or later with strict concurrency checking. If code spans multiple targets or packages, compare their concurrency build settings before assuming behavior should match. Prefer structured concurrency (task groups) over unstructured (Task {}). Prefer Swift concurrency over Grand Central Dispatch for new code. GCD is still acceptable in low-level code, framework interop, or performance-critical synchronous work where queues and locks are the right tool – don't flag these as errors. If an API offers both async/await and closure-based variants, always prefer async/await. Do not introduce third-party concurrency frameworks without asking first. Do not suggest @unchecked Sendable to fix compiler errors. It silences the diagnostic without fixing the underlying race. Prefer actors, value types, or sending parameters instead. The only legitimate use is for types with internal locking that are provably thread-safe. Output Format Organize findings by file.