swift-concurrency-expert

Analyze Swift concurrency usage for data-race hazards and unsafe actor isolation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/derKlinke/codex-config --skill swift-concurrency-expert-derklinke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swift-concurrency-expert
Source: https://github.com/derKlinke/codex-config/tree/main/skills/ios-swift-concurrency-expert
Command: npx skills add https://github.com/derKlinke/codex-config --skill swift-concurrency-expert-derklinke

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps developers review and remediate Swift Concurrency usage, addressing data-race risks and unsafe actor isolation to improve code safety and maintainability.

Core Features & Use Cases

  • Automated review: identifies actor-isolation violations, Sendable misuses, and main-actor boundary breaches.
  • Guided remediations: suggests minimal-change fixes that preserve behavior while improving concurrency safety.
  • Use Case: Apply to a SwiftUI app with complex concurrent data flows to refactor nonisolated types and add appropriate actor annotations.

Quick Start

Use the swift-concurrency-expert skill to review a Swift file and propose minimal, safe fixes for actor isolation, Sendable conformance, and main-actor boundaries.

Frequently Asked Questions about swift-concurrency-expert

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

FAQPage Schema
How do I identify data-race hazards in Swift concurrency code?

Identifying Swift concurrency data-race hazards involves analyzing actor-isolation violations, Sendable misuses, and main-actor boundary breaches. This skill reviews Swift codebases leveraging actors and Sendable closures to detect these unsafe concurrency patterns.

What is the best way to fix actor isolation violations in a SwiftUI app?

The best way to fix actor isolation violations is applying minimal-change remediations that preserve behavior. This involves refactoring nonisolated types and adding appropriate actor annotations to enforce safe concurrency boundaries.

Does this concurrency analysis support iOS and macOS apps with Sendable closures?

Yes, this concurrency analysis supports iOS and macOS apps. It specifically evaluates Swift codebases leveraging Sendable closures, actors, and main-actor boundaries to ensure safe migration patterns across these Apple platforms.

How do I ensure my Swift 6.2 concurrency refactors compile cleanly?

Ensuring Swift 6.2 concurrency refactors compile cleanly requires enforcing safe migration patterns and precise concurrency fixes. This skill proposes minimal behavioral changes that improve concurrency safety while compiling without errors.

Why do I need to review Sendable conformance for Swift concurrency?

Reviewing Sendable conformance is necessary to prevent unsafe concurrent data access. Sendable misuses often cause data-race risks, and analyzing them ensures safe type boundaries across main-actor and actor-isolated contexts.