skills.rest
jperezdelreal
jperezdelrealCOMMUNITY
Explore all skills by this author →
GitHub

swift-concurrency-pro

Detect concurrency correctness issues and async/await pitfalls in Swift code.

Updated Apr 6, 2026
Search Tags:#linting#concurrency#swift#static-analysis#code-review#async-await#actors
One-click install
npx skills add https://github.com/jperezdelreal/GymBro --skill swift-concurrency-pro-jperezdelreal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: swift-concurrency-pro
Source: https://github.com/jperezdelreal/GymBro/tree/main/.squad/skills/ios/swift-concurrency-pro
Command: npx skills add https://github.com/jperezdelreal/GymBro --skill swift-concurrency-pro-jperezdelreal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews Swift concurrency code for correctness, modern API usage, and common async/await pitfalls. Use when reading, writing, or reviewing Swift concurrency code.

Core Features & Use Cases

  • Concurrency correctness audits: Detects unsafe actor usage, data races, and non-isolated state access.
  • Modern API usage checks: Prefers async/await and structured concurrency patterns over GCD where appropriate.
  • Guided remediation: Provides concrete before/after suggestions and testing considerations for fixes.

Quick Start

Ask the analyzer to review your Swift codebase’s concurrency usage and return actionable fixes.

Frequently Asked Questions about swift-concurrency-pro

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

FAQPage Schema
How do I audit Swift concurrency for data races and unsafe actor access?▼

To audit Swift concurrency, analyze your codebase for unsafe actor usage, data races, and non-isolated state access. The review prioritizes structured concurrency patterns over unstructured tasks to ensure safe async/await implementation.

What are common async/await pitfalls in Swift structured concurrency?▼

Common async/await pitfalls include unsafe actor usage, data races, and improper task cancellation. Static analysis detects these concurrency correctness issues and highlights when unstructured tasks should be replaced with structured concurrency patterns.

Does Swift concurrency static analysis require strict concurrency checking?▼

Yes, strict concurrency checking is required. The analysis requires Swift 6.2+ with strict concurrency checking enabled to accurately identify non-isolated state access and modernize async/await API usage.

How do I fix data races and non-isolated state access in Swift actors?▼

To fix data races and non-isolated state access, use guided remediation steps that provide concrete before/after code suggestions. The analysis prioritizes structured concurrency and documents specific testing considerations for each fix.

When should I use structured concurrency over GCD in Swift?▼

You should use structured concurrency over GCD when modern API usage checks determine it is appropriate. The analysis prefers async/await and structured concurrency patterns to avoid common async/await pitfalls and unstructured task complexities.

Related Skills

Explore More Software Engineering Skills→
mikkermikker
102

swift-concurrency-expert

Assess and remediate Swift 6.2+ concurrency issues including actor isolation and Sendable safety.

Community
Advanced
PallepadehatPallepadehat
1

swift-concurrency-expert

Review and remediate Swift 6.2+ concurrency issues with actor isolation and Sendable safety.

Community
Advanced
LuminaVaultLuminaVault

swift-concurrency-pro

Analyze Swift code for concurrency correctness and Swift 6.2 standards.

Official
Advanced
javierhbrjavierhbr

swift-code-review

Review Swift code for concurrency safety, error handling, and memory management.

Community
Intermediate