⚡

// Skill profile

Swift Code Review

Name: Swift Code Review
Author: anderskev

name: swift-code-review

by anderskev · published 2026-04-01

开发工具数据处理

Total installs

Stars

★ 0

Last updated

2026-04

// Install command

$ claw add gh:anderskev/anderskev-swift-code-review

View on GitHub

// Full documentation

---

name: swift-code-review

description: Reviews Swift code for concurrency safety, error handling, memory management, and common mistakes. Use when reviewing .swift files for async/await patterns, actor isolation, Sendable conformance, or general Swift best practices.

---

# Swift Code Review

Quick Reference

| Issue Type | Reference |

|------------|-----------|

| async/await, actors, Sendable, Task | [references/concurrency.md](references/concurrency.md) |

| @Observable, @ObservationIgnored, @Bindable | [references/observable.md](references/observable.md) |

| throws, Result, try?, typed throws | [references/error-handling.md](references/error-handling.md) |

| Force unwraps, retain cycles, naming | [references/common-mistakes.md](references/common-mistakes.md) |

Review Checklist

[ ] No force unwraps (`!`) on runtime data (network, user input, files)

[ ] Closures stored as properties use `[weak self]`

[ ] Delegate properties are `weak`

[ ] Independent async operations use `async let` or `TaskGroup`

[ ] Long-running Tasks check `Task.isCancelled`

[ ] Actors have mutable state to protect (no stateless actors)

[ ] Sendable types are truly thread-safe (beware `@unchecked`)

[ ] Errors handled explicitly (no empty catch blocks)

[ ] Custom errors conform to `LocalizedError` with descriptive messages

[ ] Nested @Observable objects are also marked @Observable

[ ] @Bindable used for two-way bindings to Observable objects

When to Load References

Reviewing async/await, actors, or TaskGroups → concurrency.md

Reviewing @Observable or SwiftUI state → observable.md

Reviewing error handling or throws → error-handling.md

General Swift review → common-mistakes.md

Review Questions

1. Are async operations that could run concurrently using `async let`?

2. Could actor state change across suspension points (reentrancy bug)?

3. Is `@unchecked Sendable` backed by actual synchronization?

4. Are errors logged and presented with helpful context?

5. Could any closure or delegate create a retain cycle?

// Comments

// Related skills

More tools from the same signal band

Order food/drinks (点餐) on an Android device paired as an OpenClaw node. Uses in-app menu and cart; add goods, view cart, submit order (demo, no real payment).

Sign plugins, rotate agent credentials without losing identity, and publicly attest to plugin behavior with verifiable claims and authenticated transfers.

The philosophical layer for AI agents. Maps behavior to Spinoza's 48 affects, calculates persistence scores, and generates geometric self-reports. Give your...

日历管理数据处理

1 installs★ 0