aif-review

Name: aif-review
Availability: InStock
Author: vanyastaff

Enforce Rust coding standards and project conventions across a workspace.

2|Updated May 26, 2025

Search Tags:#code review #linting #best practices #dependency management #rust #ci

Ready to run

npx skills add https://github.com/vanyastaff/nebula --skill aif-review-vanyastaff

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aif-review
Source: https://github.com/vanyastaff/nebula/tree/main/.ai-factory/skill-context/aif-review
Command: npx skills add https://github.com/vanyastaff/nebula --skill aif-review-vanyastaff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the enforcement of critical Rust coding standards and project conventions, preventing common errors and ensuring code quality and maintainability.

Core Features & Use Cases

Automated Linting: Enforces Rust linting rules and best practices.
Dependency Management: Ensures correct layer dependency direction and prevents problematic imports.
Error Handling Standards: Mandates proper error type definitions and disallows the use of anyhow in library crates.
Use Case: Automatically flag pull requests that introduce new Rust crates without documentation or that use forbidden lint suppression patterns, ensuring a high baseline of code quality.

Quick Start

Run the aif-review skill to check the current project for rule violations.

Frequently Asked Questions about aif-review

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

FAQPage Schema

How do I enforce Rust coding standards in a CI pipeline?▼

You can enforce Rust coding standards in CI by running an automated review process that checks workspaces for unsafe code, linting violations, and dependency direction, preventing non-compliant pull requests from merging.

What are best practices for dependency management in Rust workspaces?▼

Best practices for Rust dependency management include enforcing correct inter-crate dependency direction and preventing problematic wildcard imports to maintain a clean architecture across the workspace.

How should I handle error types to pass Rust code reviews?▼

To pass Rust code reviews, you must ensure error enum completeness and avoid using the anyhow crate in library crates, mandating proper error type definitions instead of generic handlers.

Can I suppress lints in Rust pull requests?▼

You cannot use forbidden lint suppression patterns in pull requests, as automated review checks flag code that introduces new crates without documentation or violates specific lint suppression rules.

Does automated Rust linting check for documentation and unsafe code?▼

Automated Rust linting checks for missing documentation and enforces strict rules regarding unsafe code, ensuring a high baseline of code quality and maintainability across the project.