Enforce Rust formatting, linting, and safety conventions for code generation and review.
npx skills add https://github.com/Pyl-Tech/stream-coding --skill rust-pyl-tech
Please help me install this Agent Skill. Skill: rust Source: https://github.com/Pyl-Tech/stream-coding/tree/main/.agents/skills/rust Command: npx skills add https://github.com/Pyl-Tech/stream-coding --skill rust-pyl-tech
This Skill helps you prevent Rust code review churn and production failures by ensuring your specification explicitly covers Rust conventions, safety constraints, ownership/borrowing rules, and verification expectations.
cargo fmt and cargo clippy -- -D warnings to keep code style consistent and warnings treated as errors.Cow applies, and when mutation is justified.Result + ?, context-aware errors, and appropriate unit/integration/property/async testing approaches.unsafe, dependency/audit tooling expectations, and a targeted review rubric for high-severity issues.Ask your AI to generate a Rust project spec that follows the required conventions for ownership, error handling, security (including unsafe safety comments), and the code-review checklist.
High-intent search queries and answers about installing and using this skill.
You enforce Rust ownership and borrowing rules in code review by mandating specifications that document when to borrow versus own, when Cow applies, and when mutation is justified.
Configure cargo fmt and clippy gates for Rust CI pipelines by treating warnings as errors using cargo clippy -- -D warnings and enforcing rustfmt as a non-negotiable formatting check before merging code.
The best way to handle errors in production Rust applications is to mandate Result with the ? operator, provide context-aware error messages, and define appropriate unit, integration, property, and async testing patterns.
Document unsafe Rust blocks for security reviews by writing explicit invariants and safety comments that explain the security-aware reasoning behind the unsafe usage, dependencies, and audit tooling expectations.
Yes, this Rust specification approach works with existing Cargo.toml projects, applying directly to .rs modules, Cargo-based CI/linting pipelines, and production or library/application code reviews.
Your Rust code review keeps failing because your specifications lack explicit coverage of safety constraints, ownership/borrowing rules, and verification expectations required to prevent production failures and review churn.
ar4mirezGuide Rust development with ownership, error handling, and concurrency best practices.
d-o-hubFormat, lint, and audit Rust code with cargo fmt, Clippy, and cargo-audit.
agentmattersImplement Rust unit, integration, async, and property-based tests with cargo test, proptest, and mockall.
manutejExplain Rust ownership, borrowing, and concurrency models for systems programming.