rust-testing
Skill47 starsChanged 9 months agoMITView on GitHub
Use this skill for detailed, production-ready guidance in this Rust domain. How do we keep tests deterministic, fast, and meaningful?
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
Use this skill for detailed, production-ready guidance in this Rust domain.
- Distinctive: line 15
Use unit tests for logic, integration for contracts
- Distinctive: line 16
Use property tests for invariants
- Distinctive: line 17
Use loom/criterion for concurrency/perf confidence
- Distinctive: line 24
Verify with tests, linting, and scenario-specific checks.
“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
name: rust-testing description: "Rust testing expert for unit, integration, async, property-based, concurrency, and benchmark testing workflows."---
Rust Testing Skill
Use this skill for detailed, production-ready guidance in this Rust domain.
Core Question
How do we keep tests deterministic, fast, and meaningful?
Solution Patterns
- Use unit tests for logic, integration for contracts - Use property tests for invariants - Use loom/criterion for concurrency/perf confidence
Workflow
1. Reproduce and isolate the issue with a minimal failing case. 2. Choose the smallest safe design that satisfies constraints. 3. Implement with explicit ownership, errors, and boundaries. 4. Verify with tests, linting, and scenario-specific checks.
Review Checklist
- [ ] Correct behavior for both success and failure paths. - [ ] Ownership and API boundaries are explicit. - [ ] Error handling and diagnostics are actionable. - [ ] Performance-sensitive paths are measured. - [ ] Regression tests cover the changed behavior.
Common Pitfalls
- Fixing flakes with sleep - Over-mocking - Slow tests in default CI path
Verification Commands
cargo test
cargo test -- --nocapture
cargo bench
cargo nextest runRelated Skills
- rust-concurrency
- rust-performance
- rust-database
Other versions25 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 25
- loulanyue/awesome-claude-notes★ 272same name
- Fmarzochi/EGC★ 61same name
- Bitslix/BLXCode★ 15same name
- full-stack-skills/rust-skills★ 8same name
- gongyijie85/dsh-ecc★ 8same name
- aphrody-code/bxc★ 2same name
- idexal/idexal-skills★ 2same name
- ronmkr/PromptBook★ 2same name
- adxptived/Rust-Skills★ 1same name
- carvalhosauro/open-loops★ 1same name
15 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use rust-async-patterns and rust-best-practices.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
klauswgSkillrust-async-patterns
Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.
Also in 4 projects that use this
MicrosoftSkillrust-best-practices
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook. Use this skill when: (1) writing new Rust code or functions, (2) reviewing or refactoring existing Rust code, (3) deciding between borrowing vs cloning or ownership patterns, (4) implementing error handling with Result types, (5) optimizing Rust code for performance, (6) writing tests or documentation for Rust projects.
Also in 6 projects that use this
In this repository40 other files it gives its agents.
- .codex/AGENTS.mdAGENTS.md
- SKILL.mdSkill
- rust-actorSkill
- rust-anti-patternSkill
- rust-async-patternSkill
- rust-asyncSkill
- rust-authSkill
- rust-cacheSkill
- rust-codingSkill
- rust-concurrencySkill
- rust-constSkill
- rust-coroutineSkill
- rust-databaseSkill
- rust-distributedSkill
- rust-dpdkSkill
- rust-ebpfSkill
- rust-ecosystemSkill
- rust-embeddedSkill
- rust-error-advancedSkill
- rust-errorSkill
- rust-ffiSkill
- rust-gpuSkill
- rust-learnerSkill
- rust-lifetime-complexSkill
- rust-linear-typeSkill
- rust-macroSkill
- rust-middlewareSkill
- rust-mutabilitySkill
- rust-observabilitySkill
- rust-ownershipSkill
- rust-performanceSkill
- rust-pinSkill
- rust-resourceSkill
- rust-skill-indexSkill
- rust-skillSkill
- rust-type-drivenSkill
- rust-unsafeSkill
- rust-webSkill
- rust-xacmlSkill
- rust-zero-costSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

