swift-concurrency-pro

Solid

Reviews Swift code for concurrency correctness, modern API usage, and common async/await pitfalls. Use when reading, writing, or reviewing Swift concurrency code.

AI & Automation 5 stars 0 forks Updated 5 days ago MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
26
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

Review Swift concurrency code for correctness, modern API usage, and adherence to project conventions. Report only genuine problems - do not nitpick or invent issues. Review process: 1. Scan for known-dangerous patterns using `references/hotspots.md` to prioritize what to inspect. 1. Check for recent Swift 6.2 concurrency behavior using `references/new-features.md`. 1. Validate actor usage for reentrancy and isolation correctness using `references/actors.md`. 1. Ensure structured concurrency is preferred over unstructured where appropriate using `references/structured.md`. 1. Check unstructured task usage for correctness using `references/unstructured.md`. 1. Verify cancellation is handled correctly using `references/cancellation.md`. 1. Validate async stream and continuation usage using `references/async-streams.md`. 1. Check bridging code between sync and async worlds using `references/bridging.md`. 1. Review any legacy concurrency migrations using `references/interop.md`. 1. Cross-check against common failure modes using `references/bug-patterns.md`. 1. If the project has strict-concurrency errors, map diagnostics to fixes using `references/diagnostics.md`. 1. If reviewing tests, check async test patterns using `references/testing.md`. If doing a partial review, load only the relevant reference files. ## Core Instructions - Target Swift 6.2 or later with strict concurrency checking. - If code spans multiple targets or packages, compare their concurrency build setting...

Details

Author
kelvinkosbab
Repository
kelvinkosbab/AppBootstrapAI
Created
3 months ago
Last Updated
5 days ago
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

swift-concurrency

Resolve Swift concurrency compiler errors, adopt approachable concurrency (SE-0466), and write data-race-safe async code. Use when fixing Sendable conformance errors, actor isolation warnings, or strict concurrency diagnostics; when adopting default MainActor isolation, @concurrent, nonisolated(nonsending), or Task.immediate; when designing actor-based architectures, structured concurrency with TaskGroup, or background work offloading; or when migrating from @preconcurrency to full Swift 6 strict concurrency.

1 Updated today
eric-sabe
Code & Development Listed

swift-concurrency

Diagnose data races, convert callback-based code to async/await, implement actor isolation patterns, resolve Sendable conformance issues, and guide Swift 6 migration. Use when developers mention: (1) Swift Concurrency, async/await, actors, or tasks, (2) "use Swift Concurrency" or "modern concurrency patterns", (3) migrating to Swift 6, (4) data races or thread safety issues, (5) refactoring closures to async/await, (6) @MainActor, Sendable, or actor isolation, (7) concurrent code architecture or performance optimization, (8) concurrency-related linter warnings (SwiftLint or similar; e.g. async_without_await, Sendable/actor isolation/MainActor lint).

1 Updated today
patrickserrano
Code & Development Listed

swift-concurrency

Diagnose data races, convert callback-based code to async/await, implement actor isolation patterns, resolve Sendable conformance issues, fix @Observable + @MainActor interaction problems, and guide Swift 6 migration. Use when developers mention: (1) Swift Concurrency, async/await, actors, or tasks, (2) "use Swift Concurrency" or "modern concurrency patterns", (3) migrating to Swift 6, (4) data races or thread safety issues, (5) refactoring closures to async/await, (6) @MainActor, Sendable, or actor isolation, (7) @Observable with concurrency or actor isolation, (8) concurrent code architecture or performance optimization, (9) concurrency-related linter warnings (SwiftLint or similar), (10) SwiftUI view model patterns with Observation framework.

0 Updated 3 days ago
pszypowicz