swift6-strict-concurrency
This skill should be used when the user asks to "migrate to Swift 6", "enable strict concurrency", "fix Sendable errors", "add @MainActor", "resolve data race warnings", "implement actor isolation", "configure complete concurrency checking", "fix Swift 6 warnings", "make class Sendable", "handle @Sendable closures", "Swift 6 に移行", "Strict Concurrency を有効化", "Sendable エラーを修正", "@MainActor を追加", "データ競合警告を解決", "アクター分離を実装", "完全な並行性チェックを設定", "Swift 6 警告を修正", "クラスを Sendable にする", "@Sendable クロージャを扱う", or needs guidance on Swift 6 strict concurrency migration, Sendable protocol implementation, actor isolation patterns, data race safety, and migration strategies from Swift 5 to Swift 6.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Features and purpose
This skill should be used when the user asks to "migrate to Swift 6", "enable strict concurrency", "fix Sendable errors", "add @MainActor", "resolve data race warnings", "implement actor isolation", "configure complete concurrency checking", "fix Swift 6 warnings", "make class Sendable", "handle @Sendable closures", "Swift 6 に移行", "Strict Concurrency を有効化", "Sendable エラーを修正", "@MainActor を追加", "データ競合警告を解決", "アクター分離を実装", "完全な並行性チェックを設定", "Swift 6 警告を修正", "クラスを Sendable にする", "@Sendable クロージャを扱う", or needs guidance on Swift 6 strict concurrency migration, Sendable protocol implementation, actor isolation patterns, data race safety, and migration strategies from Swift 5 to Swift 6.
Quick start
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
Guides ↗Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-21
- Index updated
- 2026-01-26
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!