Does it support error handling best practices?

Absolutely. The skill checks if errors are properly mapped or caught, especially within flatMap operations, to prevent the main publisher chain from dying unexpectedly.

How does this skill detect memory leaks in Combine?

It specifically scans your code for sink and assign calls, checking if [weak self] is utilized when self owns the cancellable and ensuring AnyCancellables are properly stored rather than discarded.

When should I use the combine-code-review skill?

You should trigger this skill whenever you are reviewing or writing code that imports the Combine framework, specifically when dealing with PassthroughSubject, @Published properties, or complex operator chains.

Can it help with thread management for UI updates?

Yes, it identifies when UI-related updates are performed without a receive(on: DispatchQueue.main) operator, which is essential for preventing crashes and UI glitches in iOS apps.

Combine Framework Code Review

Name: Combine Framework Code Review
Author: existential-birds

byexistential-birds

•

Mobile Development

Analyzes Swift Combine code to identify memory leaks, operator misconfigurations, and improper error handling in reactive streams.

Acerca de

This Claude Code skill provides specialized static analysis and review for Apple's Combine framework, ensuring your reactive iOS or macOS code is performant and memory-efficient. It automates the detection of common pitfalls such as retain cycles in sink closures, improper use of assign(to:on:), and unhandled errors that can prematurely terminate reactive chains. By enforcing industry best practices for Subjects, Publishers, and threading, it helps developers build more robust and maintainable reactive architectures.

Características Principales

Validates operator chains to prevent accidental stream termination during errors
Enforces type-erasure best practices using eraseToAnyPublisher()
14 GitHub stars
Detects potential retain cycles and missing [weak self] references in subscriptions
Ensures thread safety by verifying main-thread delivery for UI updates
Audits PassthroughSubject and CurrentValueSubject usage for state and event logic

Casos de Uso

Reviewing complex reactive data pipelines in iOS or macOS applications
Auditing error handling strategies to ensure application stability under failure conditions
Troubleshooting memory leaks related to AnyCancellable storage and subscriptions

Acerca de

Características Principales

Validates operator chains to prevent accidental stream termination during errors
Enforces type-erasure best practices using eraseToAnyPublisher()
14 GitHub stars
Detects potential retain cycles and missing [weak self] references in subscriptions
Ensures thread safety by verifying main-thread delivery for UI updates
Audits PassthroughSubject and CurrentValueSubject usage for state and event logic

Casos de Uso

Reviewing complex reactive data pipelines in iOS or macOS applications
Auditing error handling strategies to ensure application stability under failure conditions
Troubleshooting memory leaks related to AnyCancellable storage and subscriptions