swift-concurrency

Diagnose Swift concurrency issues and generate migration plans for async/await.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/pszypowicz/claude-skills --skill swift-concurrency-pszypowicz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swift-concurrency
Source: https://github.com/pszypowicz/claude-skills/tree/main/plugins/swift-concurrency/skills/swift-concurrency
Command: npx skills add https://github.com/pszypowicz/claude-skills --skill swift-concurrency-pszypowicz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and mitigate Swift concurrency issues in codebases by analyzing isolation boundaries, data races, and migration requirements.

Core Features & Use Cases

  • Guidance for migrating from callbacks to async/await, applying actor isolation, Sendable conformance, and UI patterns (including @Observable) across Swift 5/6 projects.
  • Concrete, step-by-step migration plans with guardrails, error handling, and testing recommendations to ensure safe concurrency.
  • Best practices for using concurrency primitives (Task, withTaskGroup, Mutex, actors) and linting rules to prevent data races.

Quick Start

Analyze your Swift project to identify concurrency problems and generate a practical migration plan.

Frequently Asked Questions about swift-concurrency

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate callback-based Swift code to async/await?

Migrating callback-based Swift code to async/await involves analyzing isolation boundaries and replacing completion handlers with structured concurrency. This Skill generates concrete, step-by-step migration plans with guardrails and validation checks to ensure safe async/await adoption.

What is the best way to resolve Swift data races using actor isolation?

Resolving Swift data races with actor isolation requires analyzing shared mutable state across concurrency boundaries. This Skill diagnoses data race risks and provides guidance for applying actor isolation and Sendable conformance to ensure safe, scalable concurrency across Swift 5/6 projects.

When do I need to apply Sendable conformance in Swift?

Sendable conformance is needed when passing data across Swift concurrency boundaries to prevent data races. This Skill analyzes your codebase to identify where Sendable conformance is required and delivers concrete migration steps to enforce safe isolation.

Does this Skill support Swift 6 concurrency migration for existing projects?

Yes, this Skill supports Swift 6 concurrency migration by analyzing existing codebases for isolation boundaries and data races. It delivers guardrailed migration steps, error handling, and testing recommendations tailored for Swift 5 and 6 projects.

Why are my Swift concurrency tasks experiencing data races?

Swift concurrency tasks experience data races when isolation boundaries are improperly configured or Sendable constraints are missing. This Skill diagnoses your codebase to identify isolation boundary violations and provides concrete steps to apply actor isolation and concurrency primitives.

What linting rules should I use to prevent Swift concurrency issues?

Linting rules for Swift concurrency should target data race prevention, Sendable conformance, and actor isolation boundaries. This Skill recommends best practices and linting configurations alongside step-by-step migration plans to maintain safe concurrency.