What problem does it solve?
Reviewing pull requests for architectural consistency is time-consuming and easy to overlook, especially in multi-crate Rust projects with strict dependency direction and trait boundary rules. This Skill automates an advisory architecture review of any PR diff against the project's documented constraints.
Core Features & Use Cases
- Dependency Direction Validation: Checks Cargo.toml changes and use statements to ensure dependencies flow inward toward the API crate, never outward.
- Trait Boundary and Extension Pattern Checks: Detects hardcoding around trait abstractions, downcasting, and implementations that bypass the factory registration pattern.
- Advisory-Only Reporting: Writes a structured review artifact to tmp/arch-review-<N>.md and posts it as a non-blocking PR comment only after explicit human approval.
- Use Case: A contributor opens a PR adding a new channel implementation. Run the check to verify it registers via the factory pattern, lives in the correct crate, and does not violate any of the seven core engineering constraints before human review.
Quick Start
Ask the assistant to run an architecture check on a pull request by saying: run arch-check on PR number 1234 and show me the advisory review.
