skills.rest
ulpi-io
ulpi-ioOFFICIAL
Explore all skills by this author →
GitHub

review-crate

Audit a Rust crate end to end and document evidence-backed issues.

4|3|Updated Mar 15, 2026
Search Tags:#code review#issue tracking#security review#rust#bug detection#cargo test#crate audit
One-click install
npx skills add https://github.com/ulpi-io/skills --skill review-crate-ulpi-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-crate
Source: https://github.com/ulpi-io/skills/tree/main/review-crate
Command: npx skills add https://github.com/ulpi-io/skills --skill review-crate-ulpi-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents incomplete or speculative Rust crate reviews by requiring a full file-by-file audit, test execution, duplicate checking, and evidence-backed issue reporting.

Core Features & Use Cases

  • Complete Crate Review: Enumerates and reads every file in one Rust crate instead of sampling selected source files.
  • Verification and Issue Tracking: Runs the crate's tests, checks the canonical issue file, and records only new findings with severity, category, exact file and line references, and fix direction.
  • Use Case: Ask it to audit a specific crate before release to identify correctness bugs, panic risks, validation gaps, race conditions, data corruption risks, and meaningful coverage gaps.

Quick Start

Use the review-crate skill to perform a complete evidence-backed audit of the Rust crate at the specified path.

Frequently Asked Questions about review-crate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform a complete Rust crate audit before release?▼

You can audit a Rust crate end to end by reading every file, running cargo tests, checking the canonical issue file, and documenting findings with exact file and line evidence to prevent speculative or incomplete reviews.

What is evidence-backed code review for Rust crates?▼

Evidence-backed code review means every identified issue—such as correctness bugs, panic risks, or race conditions—must include exact file and line references, severity, category, and fix direction instead of speculative observations.

Can I use this approach to review multiple Rust crates at once?▼

No, this approach is designed for deep reviews of individual crates and explicitly excludes multi-crate sweeps or branch-diff reviews to ensure thorough file-by-file auditing and test execution.

How do I identify safety and data corruption risks in a Rust crate?▼

To identify safety and data corruption risks, you run the crate's cargo tests, read every file completely, and record validation gaps, race conditions, and panic risks with exact file and line evidence.

Does a thorough Rust crate review require running cargo test?▼

Yes, running cargo test is required during a thorough crate review to verify behavior, identify meaningful coverage gaps, and ensure documented findings reflect actual execution results rather than assumptions.

What limitations exist when auditing Rust crates for reliability risks?▼

Limitations include excluding branch-diff reviews and multi-crate sweeps, requiring a full file-by-file read of one crate, and mandating exact file and line evidence for every new finding.

Related Skills

Explore More Software Engineering Skills→
devrelaicomdevrelaicom
37

midnight-verify:verify-by-ledger-source

Verify ledger claims by tracing them to Rust source files and paths.

Official
Advanced
polsegupolsegu

day-one-patch

Scope, prioritize, implement, and QA-gate urgent post-gold-master game fixes.

Community
Advanced
icartshicartsh
4

code-analyze

Analyze .NET solutions for code quality, security, and dependency issues.

Community
Advanced
doitiandoitian
14

crates-trusted-publishing

Automate Rust crate publishing to crates.io via OIDC trusted publishing.

Community
Intermediate