Swift concurrency diagnostics and migration choices can be difficult to interpret. This skill provides targeted guidance for isolation, Sendable, tasks, testing, and Swift 6 refactoring.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "swift-concurrency" from https://skillstore.io/skills/avdlee-swift-concurrency.md and its manifest at https://skillstore.io/api/skills/avdlee-swift-concurrency/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.
Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
All 129 static findings are false positives caused by Markdown syntax, Swift examples, local documentation links, and ordinary concurrency terminology. No prompt injection, malicious execution, reconnaissance, data exfiltration, or unsafe path handling was found.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
AvdLee. (2026). swift-concurrency security audit report (audit version 12) [Author version unspecified]. Skillstore. https://skillstore.io/skills/avdlee-swift-concurrency/audits/12
BibTeX citation
@techreport{avdlee-avdlee-swift-concurrency-2026,
author = {AvdLee},
title = {swift-concurrency security audit report (audit version 12)},
institution = {Skillstore},
year = {2026},
number = {12},
url = {https://skillstore.io/skills/avdlee-swift-concurrency/audits/12},
note = {Author version unspecified}
}
CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "swift-concurrency security audit report (audit version 12)"
version: "unspecified"
type: report
authors:
- name: "AvdLee"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/avdlee-swift-concurrency/audits/12"
identifiers:
- type: other
value: "skillstore:avdlee-swift-concurrency:audit:12"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this scoreEvidence Confidence: High
45
Architecture
85
Maintainability
87
Content
81
Community
83
Spec Compliance
What You Can Build
Resolve a compiler diagnostic
Identify the isolation or Sendable boundary behind one diagnostic and propose a focused correction.
Modernize an asynchronous API
Convert callback-based workflows to async/await with clear error, cancellation, and testing behavior.
Plan a Swift 6 migration
Sequence concurrency changes by module, diagnostic category, verification step, and documented safety invariant.
Try These Prompts
Explain a diagnostic
Explain this Swift concurrency diagnostic: [diagnostic]. Ask for required project settings before proposing the smallest fix.
Refactor callback code
Refactor [callback API] to async/await while preserving errors, cancellation, isolation, and behavior. Explain each change and propose focused tests.
Review isolation boundaries
Review [files] for actor isolation, Sendable crossings, task structure, cancellation, and UI ownership. Recommend the smallest behavior-preserving corrections.
Plan a Swift 6 migration
Create a phased Swift 6 concurrency migration for [module]. Include settings, diagnostic groups, safety invariants, tests, performance checks, and rollback points.
Best Practices
Provide the exact diagnostic, minimal affected code, and relevant project settings.
State ownership, UI requirements, and behavior that must remain unchanged.
Build and test after each diagnostic category or migration step.
Avoid
Do not apply MainActor broadly without confirming UI ownership.
Do not use detached tasks or unchecked Sendable as default fixes.
Do not combine unrelated migration changes before verifying behavior.
Frequently Asked Questions
Which Swift concurrency problems can this skill address?
It covers async/await, tasks, actors, Sendable, isolation, testing, Core Data, memory, performance, and common migration diagnostics.
Why are project settings required?
Language mode, strict checking, default isolation, and upcoming features change compiler behavior and the correct fix.
Can it generate a complete refactor?
It can propose focused changes, but confirmation requires the project, compiler diagnostics, builds, and tests.
Does it support projects before Swift 6?
Yes. Guidance depends on the active Swift language mode and enabled concurrency checks.
Can it help with Core Data concurrency?
Yes. It explains context isolation, object identifier transfer, custom executors, and Sendable boundaries.
How should recommendations be verified?
Rebuild after focused changes, run concurrency-sensitive tests, inspect cancellation and lifetime behavior, and profile performance claims.