rust-concurrency

To find Rust concurrency bugs, audit code for anti-patterns like holding MutexGuard across .await, using Rc/RefCell across spawn boundaries, and spawning non-Send futures. This skill identifies Send/Sync violations and proposes safe replacements like tokio::sync::Mutex.

Holding a MutexGuard across an await point can cause deadlocks and block async executors. This skill detects this anti-pattern and requires safe replacements such as tokio::sync::Mutex or tokio::spawn_blocking to maintain async concurrency safety.

Preventing deadlocks requires analyzing lock acquisition order across threads. This skill detects deadlock risks from inconsistent lock ordering in Rust concurrency code and guides remediation by enforcing consistent lock patterns and safe state sharing.

Use tokio::spawn_blocking for blocking operations in async contexts to avoid starving executors. This skill identifies blocking behaviors in async Rust code and enforces safe replacements like spawn_blocking to ensure reliable concurrency.

Using Rc or RefCell across thread or task boundaries breaks Send/Sync guarantees and causes concurrency issues. This skill surfaces these non-thread-safe type violations across spawns and proposes safe alternatives for shared state management.

Auditing a Rust codebase for async concurrency anti-patterns involves checking for MutexGuard across await, blocking operations, and Send/Sync violations. This skill applies these detection patterns during code reviews to improve multi-threaded application reliability.