productdevbook/skills (apollo-rust-review)

Apollo's Rust best practices as a review standard — ownership and borrowing, clone discipline, clippy policy, error handling at crate vs binary boundaries, tests as behaviour documentation, generics vs dispatch, the type-state pattern, comments vs docs, and pointers. Read when REVIEWING Rust — a PR, a diff, or a "is this idiomatic / can this be simpler" question — and when deciding whether a clone, an allow, an unwrap or an allocation should survive review. Carries a severity matrix (P0-P3) for ranking what is found, and a set of rejection triggers. For designing a public API surface, shaping an error type from scratch, or laying out a workspace, read rust-guidelines instead; this one judges code that already exists.

Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.

Source:

github.com/productdevbook/skills

Version:

1.0.0

Provenance:

Found by crawling (provenance, not a security rating)

We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.

2 critical findings reported by agent-audit-kit. The composite score alone does not reflect this — read the per-scanner reports below.