What problem does it solve?
AI coding agents often apply lazy, cosmetic fixes to Rust code when tasked with resolving audit findings, code review comments, lint errors, or failing tests—such as blanket lint suppressions, empty safety comments, or band-aids that don't address the root cause, leading to recurring issues and broken architecture.
Core Features & Use Cases
- 3-way fix category enforcement: Requires explicit selection of root-cause, local correctness, or annotation fixes for every finding, eliminating vague "fixed the lint" reporting.
- Forbidden pattern guardrails: Blocks lazy fix patterns like empty SAFETY comments, unilateral workspace changes from leaf crates, and unannounced behavioral changes.
- Cross-crate coordination: Mandates explicit coordination requests for breaking changes to public APIs or shared workspace abstractions to avoid downstream breakage.
- Use case: Use when applying fixes to Rust code from any audit, code review, lint sweep, or failing-test triage task, especially for workspaces with strict quality and GPU discipline policies.
Quick Start
Use the rust-fix-discipline skill to apply correct, non-cosmetic fixes to all findings in your latest Rust code audit, following the required pre-fix context review and verification steps.
