sc-rust

Rust code quality auditor. Detects the project stack via sniff (01-scan), loads the applicable Rust knowledge pivots from the plugin, and delegates a structured code review to aidd-dev:reviewer using the pivots as acceptance criteria. Use when the user asks to: audit Rust code, check Rust best practices, review code quality, check idiomatic Rust, audit Axum/Actix conventions, check ownership patterns, clippy compliance, or invokes /sc-rust:audit. Does not install any files to .claude/rules/.

Analyzes the Rust codebase for idiomatic Rust gaps, ownership pattern issues, and design opportunities, then produces a prioritized improvement plan. Covers proper error handling (anyhow/thiserror, ? operator), iterator chaining over manual loops, trait-based design, builder pattern, newtype pattern, excessive cloning, unwrap() in non-test code, and async correctness. Use when the user says "how can I improve this", "is this idiomatic Rust", "find anti-patterns", "code quality", "refactoring suggestions", "too many clones". Do NOT use for performance (web-optimize), data layer (data-optimize), edition migration (legacy), or line-by-line code review (aidd-dev:05-review).

Scans Rust code for edition-specific patterns and deprecated APIs, then migrates to a target edition (2015 → 2018 → 2021 → 2024) or updates breaking crate API changes (tokio 0.x → 1.x, diesel 1.x → 2.x, failure → anyhow/thiserror, futures 0.1 → async/await). Detects extern crate declarations, old module syntax (mod.rs), try!() macro, pre-NLL borrow patterns, and deprecated std APIs. Use when the user says "migrate to Rust 2021", "upgrade edition", "this is old Rust", "update tokio", "replace failure crate", or when rustc produces edition warnings. Do NOT use for dependency management (Cargo), performance optimization (web-optimize), or general refactoring unrelated to Rust edition/API compatibility.

Analyzes Rust application logs across three environments: host filesystem (local), Docker containers (docker), and remote production server (prod via SSH). Works with tracing subscriber output (compact, pretty, JSON), env_logger output, actix-web/axum/tower-http request logs, and panic! backtraces. Auto-discovers Docker containers running the Rust binary. Use when the user says "check logs", "Rust errors", "find in logs", "log summary", "panics in prod", "analyze logs", "what's wrong in prod", "tracing output". Do NOT use for application debugging (use aidd-dev:08-debug), cargo build errors (run cargo check/clippy directly), or performance profiling.

Rust stack detector. Reads Cargo.toml (or workspace members) to detect the web framework (Axum, Actix-web) and data crates (SQLx, Diesel). Uses a two-tier model: capability pivots (Rust idioms) are loaded at audit time by /sc-rust:audit and never written to disk; perf pivots (for web-optimize) and data pivots (for data-optimize) are installed selectively to .claude/rules/07-quality/. Emits a pivot manifeste for use by /sc-rust:audit. Reports gaps when a capability is detected but no matching plugin pivot exists. Do NOT use to update a single rule manually — edit it directly instead.