What problem does it solve? Rust database access code can hide SQL injection paths, query/schema mismatches, incorrect nullability handling, wrong fetch cardinality, N+1 query patterns, and database rows leaking into public API responses. This Skill provides a structured review workflow that traces concrete consequences before reporting findings, so reviews stay precise and actionable. ## Core Features & Use Cases - SQLx-first review workflow: Inspects query macros, runtime query APIs, parameter binding, result decoding, fetch semantics, and rows_affected handling with severity-ranked findings. - Fallback database stacks: Applies equivalent rules for Diesel, SeaORM, and raw drivers (tokio-postgres, rusqlite, mysql) when SQLx is not the active stack. - DTO boundary checks: Detects database row types (FromRow, *Row, *Record) leaking into HTTP/GraphQL response DTOs with sensitive fields. - Use Case: A reviewer runs the skill on a pull request touching repository code and receives line-specific findings such as an interpolated ORDER BY clause, a fetch_one on a non-unique predicate, or an unbounded fetch_all behind a public endpoint, each with a concrete safer rewrite. ## Quick Start Ask the agent to review your current Rust working changes for SQLx query safety issues and report findings with file locations without editing code.
