rust-architecture-review

Review Rust module boundaries, dependencies, ownership, and public APIs for structural findings.

2|Updated May 6, 2026
One-click install
npx skills add https://github.com/bpcakes/jig-skills --skill rust-architecture-review-bpcakes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-architecture-review
Source: https://github.com/bpcakes/jig-skills/tree/main/plugins/jig-rust/skills/rust-architecture-review
Command: npx skills add https://github.com/bpcakes/jig-skills --skill rust-architecture-review-bpcakes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Rust codebases accumulate structural debt in module organization, crate dependencies, visibility, and trait design that routine code reviews miss. This Skill performs a focused architecture assessment of a Rust diff, file set, or snippet and reports evidence-backed structural findings instead of style opinions. ## Core Features & Use Cases - Boundary investigation: Examines cohesion, nesting, dependency cycles, visibility and re-exports, trait cohesion, type design, conversions, and compatibility policy. - Evidence standard: Treats smells as investigation signals only, requiring concrete usage, consequences, and counterevidence before reporting a finding. - Scoped review: Defaults to staged and unstaged changes when no target is given, and follows neighbors only to validate affected boundaries. - Use Case: Ask for an architecture review of a branch that splits a large crate into modules, and receive findings with severity, locations, intended boundaries, counterevidence, and minimal incremental remedies. ## Quick Start Ask the agent to review the architecture of your current Rust working changes and report findings with file locations without editing code.

Frequently Asked Questions about rust-architecture-review

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

FAQPage Schema
How do I review Rust module architecture in a pull request?

Invoke the skill on the diff or named files and it inspects module cohesion, dependency cycles, visibility, and trait design. Findings include severity, locations, evidence, and the smallest incremental remedy.

What does a Rust architecture review check for?

It checks cohesion and nesting, dependency cycles and layer violations, visibility through re-exports, trait and dispatch design, type and state modeling, conversions and errors, and compatibility policy such as sealing or non_exhaustive.

Does the Rust architecture review edit my code?

No, review-only requests produce findings and proposals without modifying files. Refactors are implemented only when the user explicitly requests changes.

When should I not use an architecture review skill?

Do not select it for routine coding, bug fixes, explanations, or general code reviews without an architectural focus. It is intended only for explicit structural design assessments of modules, crates, dependencies, ownership, or public APIs.

Why does the review report no findings for my Rust changes?

No supported findings is a valid result. Smells like deep nesting or large traits are only investigation signals, and the skill reports a defect only with concrete usage evidence, consequences, and considered counterevidence.