swift-expert

Review Swift code for concurrency, SwiftUI, memory, and test coverage issues.

34|6|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/Viniciuscarvalho/swift-code-reviewer-skill --skill swift-expert-viniciuscarvalho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swift-expert
Source: https://github.com/Viniciuscarvalho/swift-code-reviewer-skill/tree/main/skills/swift-expert
Command: npx skills add https://github.com/Viniciuscarvalho/swift-code-reviewer-skill --skill swift-expert-viniciuscarvalho

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps review and improve Swift and SwiftUI code by catching concurrency mistakes, memory risks, protocol design flaws, and missing test coverage before they become production issues.

Core Features & Use Cases

  • Modern Swift guidance: Enforces Swift 6+, async/await, structured concurrency, actor isolation, Sendable safety, and main-actor UI rules.
  • SwiftUI review support: Evaluates state management, view composition, environment usage, custom modifiers, and async view loading patterns.
  • Architecture and reliability checks: Validates protocol-oriented design, memory management, performance tradeoffs, and test strategy for app and server-side Swift code.
  • Use case: Review a feature branch for race conditions, retain cycles, unsafe force unwraps, and missing unit tests while suggesting concrete fixes.

Quick Start

Use the swift-expert skill to review my Swift changes and flag concurrency, SwiftUI, memory, protocol, and testing issues with actionable fixes.

Frequently Asked Questions about swift-expert

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

FAQPage Schema
How do I review Swift code for concurrency and Sendable safety issues?

Review Swift code for concurrency by enforcing strict async/await guidance, actor isolation, and Sendable safety. This catches race conditions and unsafe concurrent access before they become production issues in Swift 6 projects.

What's the best way to check SwiftUI views for memory leaks and state management flaws?

Check SwiftUI views by evaluating state management, view composition, and environment usage. This identifies memory risks like retain cycles and validates async view loading patterns to ensure reliable UI behavior.

Can I use this to review server-side Swift code for missing test coverage?

Yes, you can review server-side Swift code to identify missing test coverage. It validates protocol-oriented design and test strategy, suggesting concrete fixes for unsafe force unwraps and missing unit tests.

How does strict actor isolation improve iOS app code review?

Strict actor isolation improves code review by enforcing main-actor UI rules and structured concurrency. This prevents data races and ensures safe asynchronous execution across iOS and macOS applications.

When do I need to validate Sendable conformance in my Swift project?

Validate Sendable conformance when adopting Swift 6+ to ensure safe data passing across concurrent contexts. It prevents data races by enforcing value-semantic defaults and verifying actor isolation boundaries.

Why does my SwiftUI feature branch have retain cycles and unsafe force unwraps?

SwiftUI feature branches develop retain cycles and unsafe force unwraps from improper memory management and state handling. Code review flags these memory risks alongside protocol design flaws with actionable fixes.