swift-concurrency-pro
Skill7 starsChanged 19 days agoMITView on GitHub
Use when reading, writing, or reviewing Swift concurrency code. Reviews Swift code for concurrency correctness, modern API usage, and common async/await pitfalls.
10 other projects use a version of this, 8 of them edited.
Adopted by
Most recently taken up by
- kelvinkosbab/KozBonedited, first seen Nov 6, 2026
- molayab/swift-cli-manageredited, first seen Nov 1, 2026
- VelimirMueller/ai-development-skillsword for word, first seen Nov 1, 2026
- element-hq/element-x-iosedited, first seen Oct 8, 2026
- spatie/bloomtheir own version, first seen Sep 28, 2026
- Nelwhix/bloomedited, first seen Aug 18, 2026
Other versions10 projects use a version of this.
Word for word · 1
- VelimirMueller/ai-development-skills★ 7100% same
Edited · 8
- element-hq/element-x-ios★ 97094% same
- twostraws/Swift-Concurrency-Agent-Skill★ 52198% same
- 199-biotechnologies/swiftui-claude-skills★ 798% same
- kelvinkosbab/KozBon★ 598% same
- molayab/swift-cli-manager★ 398% same
- ghostineyt/Swift-Concurrency-Agent-Skill★ 198% same
- molayab/swift-ai-provider-kit★ 198% same
- Nelwhix/bloom★ 098% same
Wrote their own version · 1
- spatie/bloom★ 52same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository156 other files it gives its agents.
- skills/swift/swiftui-design-principles/AGENTS.mdAGENTS.md
- skills/swift/ios-code-audit/CLAUDE.mdCLAUDE.md
- skills/swift/swift-focusengine-pro/llms.txtllms.txt
- build-llm-seamSkill
- build-mcp-serverSkill
- build-rag-pipelineSkill
- secure-llm-featuresSkill
- set-up-llm-evalsSkill
- build-nextjs-backendSkill
- build-supabase-edge-functionSkill
- configure-backend-testsSkill
- design-http-apiSkill
- harden-backendSkill
- scaffold-fastapi-serviceSkill
- scaffold-go-serviceSkill
- scaffold-hono-serviceSkill
- secure-supabase-rlsSkill
- set-up-backend-authSkill
- set-up-background-jobsSkill
- set-up-databaseSkill
- set-up-nextjs-supabase-authSkill
- set-up-observabilitySkill
- set-up-supabaseSkill
- build-cliSkill
- release-cliSkill
- set-up-dev-toolchainSkill
- audit-securitySkill
- audit-toolchainSkill
- extend-skillsetSkill
- promote-releaseSkill
- set-up-stack-profileSkill
- write-commit-messagesSkill
- write-pull-requestsSkill
- analyze-complexitySkill
- apply-algorithmsSkill
- apply-design-patternsSkill
- apply-design-principlesSkill
- apply-solidSkill
- choose-data-structureSkill
- debug-systematicallySkill
- enforce-dependency-ruleSkill
- refactor-safelySkill
- slice-and-estimateSkill
- write-clean-testsSkill
- write-readable-codeSkill
- clean-frontend-scaffoldingSkill
- configure-accessibilitySkill
- configure-analyticsSkill
- configure-ciSkill
- configure-error-trackingSkill
- configure-lintingSkill
- configure-test-stackSkill
- configure-typescriptSkill
- create-moduleSkill
- optimize-performanceSkill
- scaffold-frontend-projectSkill
- set-up-authSkill
- set-up-design-systemSkill
- set-up-document-headSkill
- set-up-error-boundariesSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 4 are common, 0 are distinctive, and 10 are very specific to this project.
4
Common
Most of the 9 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Check for recent Swift 6.2 concurrency behavior using references/new-features.md.
- Very specific: line 17
Ensure structured concurrency is preferred over unstructured where appropriate using references/structured.md.
- Very specific: line 18
Check unstructured task usage for correctness using references/unstructured.md.
- Very specific: line 19
Verify cancellation is handled correctly using references/cancellation.md.
- Very specific: line 21
Check bridging code between sync and async worlds using references/bridging.md.
- Very specific: line 24
If the project has strict-concurrency errors, map diagnostics to fixes using references/diagnostics.md.
- Very specific: line 25
If reviewing tests, check async test patterns using references/testing.md.
- Common: line 27
If doing a partial review, load only the relevant reference files.
- Common: line 33
If code spans multiple targets or packages, compare their concurrency build settings before assuming behavior should match.
- Very specific: line 34
Prefer structured concurrency (task groups) over unstructured (Task {}).
- Common: line 35
Prefer Swift concurrency over Grand Central Dispatch for new code.
- Very specific: line 36
If an API offers both async/await and closure-based variants, always prefer async/await.
- Common: line 37
Do not introduce third-party concurrency frameworks without asking first.
- Very specific: line 38
Do not suggest @unchecked Sendable to fix compiler errors.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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:
- Scan for known-dangerous patterns using
references/hotspots.mdto prioritize what to inspect. - Check for recent Swift 6.2 concurrency behavior using
references/new-features.md. - Validate actor usage for reentrancy and isolation correctness using
references/actors.md. - Ensure structured concurrency is preferred over unstructured where appropriate using
references/structured.md. - Check unstructured task usage for correctness using
references/unstructured.md. - Verify cancellation is handled correctly using
references/cancellation.md. - Validate async stream and continuation usage using
references/async-streams.md. - Check bridging code between sync and async worlds using
references/bridging.md. - Review any legacy concurrency migrations using
references/interop.md. - Cross-check against common failure modes using
references/bug-patterns.md. - If the project has strict-concurrency errors, map diagnostics to fixes using
references/diagnostics.md. - 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 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/awaitand closure-based variants, always preferasync/await. - Do not introduce third-party concurrency frameworks without asking first.
- Do not suggest
@unchecked Sendableto fix compiler errors. It silences the diagnostic without fixing the underlying race. Prefer actors, value types, orsendingparameters instead. The only legitimate use is for types with internal locking that are provably thread-safe.
Output Format
Organize findings by file. For each issue:
- State the file and relevant line(s).
- Name the rule being violated.
- Show a brief before/after code fix.
Skip files with no issues. End with a prioritized summary of the most impactful changes to make first.
Example output:
DataLoader.swift
Line 18: Actor reentrancy – state may have changed across the await.
// Before
actor Cache {
var items: [String: Data] = [:]
func fetch(_ key: String) async throws -> Data {
if items[key] == nil {
items[key] = try await download(key)
}
return items[key]!
}
}
// After
actor Cache {
var items: [String: Data] = [:]
func fetch(_ key: String) async throws -> Data {
if let existing = items[key] { return existing }
let data = try await download(key)
items[key] = data
return data
}
}Line 34: Use withTaskGroup instead of creating tasks in a loop.
// Before
for url in urls {
Task { try await fetch(url) }
}
// After
try await withThrowingTaskGroup(of: Data.self) { group in
for url in urls {
group.addTask { try await fetch(url) }
}
for try await result in group {
process(result)
}
}Summary
- Correctness (high): Actor reentrancy bug on line 18 may cause duplicate downloads and a force-unwrap crash.
- Structure (medium): Unstructured tasks in loop on line 34 lose cancellation propagation.
End of example.
References
references/hotspots.md- Grep targets for code review: known-dangerous patterns and what to check for each.references/new-features.md- Swift 6.2 changes that alter review advice: default actor isolation, isolated conformances, caller-actor async behavior,@concurrent,Task.immediate, task naming, and priority escalation.references/actors.md- Actor reentrancy, shared-state annotations, global actor inference, and isolation patterns.references/structured.md- Task groups over loops, discarding task groups, concurrency limits.references/unstructured.md- Task vs Task.detached, when Task {} is a code smell.references/cancellation.md- Cancellation propagation, cooperative checking, broken cancellation patterns.references/async-streams.md- AsyncStream factory, continuation lifecycle, back-pressure.references/bridging.md- Checked continuations, wrapping legacy APIs,@unchecked Sendable.references/interop.md- Migrating from GCD,Mutex/locks, completion handlers, delegates, and Combine.references/bug-patterns.md- Common concurrency failure modes and their fixes.references/diagnostics.md- Strict-concurrency compiler errors, protocol conformance fixes, and likely remedies.references/testing.md- Async test strategy with Swift Testing, race detection, avoiding timing-based tests.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

