What problem does it solve? Multi-step database writes in Rust services often break domain invariants through missing transactions, pool-versus-transaction handle confusion, SELECT-then-INSERT races, and side effects emitted before commit. This Skill gives an agent a structured review workflow to find those concrete consistency defects with file locations and fixes. ## Core Features & Use Cases - Transaction boundary analysis: Maps state-changing flows, names the invariant at risk, and verifies every query uses the transaction handle rather than a pool or separate connection. - Concurrency and isolation checks: Constructs two-request interleavings to detect check-then-write races, and recommends constraints, upserts, row locks, or serializable isolation with retry. - Side-effect and lifecycle auditing: Flags emails, webhooks, queue publishes, and cache writes that occur before commit, plus connections held across slow external calls and missing retry handling for serialization failures. - Use Case: Before merging a pull request that adds a payment flow using SQLx and PostgreSQL, run this review to confirm the debit and credit happen atomically, the idempotency row is written in the same transaction, and the webhook is sent only after commit. ## Quick Start Ask the agent to review your current working changes for SQL transaction consistency and report findings with file locations without editing code.
