swift-concurrency

Diagnose data races and migrate callback-based Swift code to async/await with actor isolation.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/jperezdelreal/GymBro --skill swift-concurrency-jperezdelreal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swift-concurrency
Source: https://github.com/jperezdelreal/GymBro/tree/main/.squad/skills/ios/swift-concurrency-expert
Command: npx skills add https://github.com/jperezdelreal/GymBro --skill swift-concurrency-jperezdelreal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Swift Concurrency offers powerful patterns but introduces data-race risks, callback-heavy code, and migration challenges. This skill helps diagnose concurrency issues, convert code to async/await, apply actor isolation, and ensure Sendable conformance across Swift 6 migrations.

Core Features & Use Cases

  • Diagnose data races and refactor callback-based code to async/await with proper actor boundaries.
  • Guide migration of legacy concurrency patterns to modern Swift 6 idioms and lint-safe constructs.
  • Use Case: When reviewing a codebase with multiple completion handlers and thread-unsafe access, apply a staged migration to async/await and MainActor-safe UI updates.

Quick Start

Begin by scanning the codebase for callback-based patterns and outline a migration path to async/await with actor isolation.

Frequently Asked Questions about swift-concurrency

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

FAQPage Schema
How do I migrate completion handlers to async/await in Swift?

To migrate completion handlers to async/await in Swift, scan your codebase for callback-based patterns and apply a staged conversion to async/await with proper actor isolation. This preserves behavior while modernizing legacy concurrency.

How do I diagnose data races during a Swift 6 migration?

Diagnose data races during a Swift 6 migration by analyzing Package.swift or pbxproj files to determine language mode and isolation boundaries. This identifies thread-unsafe access and proposes concrete migration steps with actor isolation.

What is actor isolation and when do I need it for Swift concurrency?

Actor isolation is a Swift concurrency mechanism that protects shared mutable state from data races. You need it when refactoring callback-based code to async/await to ensure thread-safe access and MainActor-safe UI updates across iOS libraries.

How do I ensure Sendable conformance across Swift 6 codebases?

Ensure Sendable conformance across Swift 6 codebases by applying lint-safe constructs and migration steps that preserve behavior. This involves analyzing isolation boundaries and converting legacy concurrency patterns to modern Swift 6 idioms.

Does this work with existing iOS libraries using closures and completion handlers?

Yes, this works with existing iOS libraries using closures and completion handlers. It analyzes your codebase to outline a migration path to async/await and actor isolation, addressing concurrency challenges across iOS and libraries during Swift 6 migration.