swift-concurrency-expert

Review Swift 6.2+ codebases for actor isolation and Sendable safety.

Updated Dec 31, 2025

Search Tags:#refactoring #concurrency #swift #code-review #sendable #swift-6.2 #actor-isolation

Ready to run

npx skills add https://github.com/diegopetrucci/ios-agents-skills --skill swift-concurrency-expert-diegopetrucci

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: swift-concurrency-expert
Source: https://github.com/diegopetrucci/ios-agents-skills/tree/main/swift-concurrency-expert
Command: npx skills add https://github.com/diegopetrucci/ios-agents-skills --skill swift-concurrency-expert-diegopetrucci

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Swift codebases often suffer from subtle concurrency issues due to actor isolation, Sendable misuse, and misapplied concurrency patterns. This skill provides a structured approach to review and remediate those issues across Swift 6.2+ projects, reducing data races and promoting safe, maintainable concurrency.

Core Features & Use Cases

Triage diagnostics to identify actor isolation violations and unsafe Sendable usage.
Apply minimal, safe fixes that preserve behavior while improving concurrency safety (e.g., @MainActor annotations, isolated conformances, actor-guarded state).
Guided remediation for common SwiftUI/Swift packages and codebases; supports both UI-bound and background tasks.

Quick Start

Provide a Swift codebase and ask it to identify concurrency issues and propose safe, minimal fixes that preserve behavior.

Frequently Asked Questions about swift-concurrency-expert

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

FAQPage Schema

How do I fix actor isolation violations in my Swift codebase?▼

Triage Swift diagnostics to identify actor isolation violations, then apply minimal fixes like @MainActor annotations or actor-guarded state to ensure safe concurrency without altering runtime behavior.

What is the best way to resolve unsafe Sendable conformance in Swift 6.2?▼

Resolving unsafe Sendable conformance involves identifying misapplied concurrency patterns and applying isolated conformances to prevent data races across modules and shared libraries.

How do I review Swift concurrency issues across SwiftUI and shared libraries?▼

Review Swift concurrency issues by analyzing SwiftUI and shared library codebases to identify Sendable misuse and actor isolation violations, then applying safe, minimal refactors to maintain stability.

Does this approach change my app's behavior when adding @MainActor annotations?▼

No, this approach enforces safe concurrency by recommending minimal, verifiable changes like @MainActor annotations that preserve your app's existing behavior while improving data safety.

When should I triage Swift 6.2 concurrency diagnostics instead of rewriting code?▼

You should triage Swift 6.2 concurrency diagnostics when you need to identify specific actor isolation violations and apply targeted, safe fixes rather than undertaking risky, broad code rewrites.