rust-testing-code-review
Reviews Rust test code for unit test patterns, integration test structure, async testing, mocking approaches, and property-based testing.
Examining code for the line that is wrong
What it does
1. Check Rust edition — Note edition in Cargo.toml (2021 vs 2024). Edition 2024 changes temporary scoping in if let and tail expressions, and makes #[expect] the preferred lint suppression 2.
Read more
Check test organization — Unit tests in #[cfg(test)] modules, integration tests in tests/ directory 3. Check async test setup — #[tokio::test] for async tests, proper runtime configuration. Check for async-trait on mocks that could use native async fn in traits 4. Check assertions — Meaningful messages, correct assertion type. Review if let assertions for edition 2024 temporary scope changes 5. Check test isolation — No shared mutable state between tests, proper setup/teardown. Prefer LazyLock over lazy_static!/once_cell for shared fixtures 6. Check coverage patterns — Error paths tested, edge cases covered
What it can touch
No script files in its folder
Its folder holds text, not programs. It changes how your AI works; it does not bring code of its own.
How we know
Listed the 5 files in the skill’s folder on GitHub; none is a script or program.
No known risk pattern found
Launch7’s automated check read all 5 text files in this skill and matched none of its risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.
How we know
Read 2026-10-05, commit d1a7489 by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.
Recently maintained
Its repository has had changes recently.
How we know
Last push to existential-birds/beagle: 2026-09-15 (20 days before the scan).
Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check
Add it to your AI
Supported. Upload it once in Claude’s settings. Works on every plan, including Free.
Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.
In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.
Make sure code execution is switched on (Settings → Capabilities). Skills need it.
Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.
How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end
More from existential-birds
All from this publisher →- adr-writing
Generate Architectural Decision Records (ADRs) following the MADR template with systematic completeness checking.
- agent-architecture-analysis
> Reference: [12-Factor Agents](https://github.com/humanlayer/12-factor-agents)
- artifact-analysis
Turn a set of local paths (or a beagle project's conventional knowledge locations) into a cited, structured extraction of insights, context, decisions, and raw detail.
- brainstorm-beagle
Turn a fuzzy idea into a comprehensive, implementation-free project spec through collaborative dialogue.
- deepagents-code-review
Reviews Deep Agents code for bugs, anti-patterns, and improvements.
