review-style

Validate changed files against rust-design, rust-impl, and rust-test style rules.

5|12|Updated Nov 24, 2025
One-click install
npx skills add https://github.com/cbgbt/bottlerocket-forest --skill review-style
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-style
Source: https://github.com/cbgbt/bottlerocket-forest/tree/main/skills/review-style
Command: npx skills add https://github.com/cbgbt/bottlerocket-forest --skill review-style

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill validates code follows project style guides, acting as a pass/fail gate during code reviews.

Core Features & Use Cases

  • Enforces project style compliance on changed files during PR reviews.
  • Applies rust-design, rust-impl, and rust-test rules relevant to the current phase.
  • Provides clear violation reports with file paths and line numbers for remediation.

Quick Start

To use the review-style skill, run it against the changed files in your PR to obtain a pass/fail verdict and a list of style violations.

Frequently Asked Questions about review-style

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

FAQPage Schema
How do I enforce Rust style compliance during code reviews?

To enforce Rust style compliance during code reviews, you can run a style validation check against changed files to return a pass/fail verdict with a list of violations and their locations for remediation.

What is the best way to gate pull requests using project style guides?

Gating pull requests with project style guides involves validating code changes against defined rules to return a pass or fail verdict, blocking merges until style violations are remediated.

How do I check code changes against Rust design and implementation rules?

Checking code changes against Rust design and implementation rules requires applying phase-appropriate rust-design, rust-impl, and rust-test rules to the modified files in your pull request.

Can I get specific file paths and line numbers for style violations in a PR?

Yes, validating code changes against project style guides provides clear violation reports that include specific file paths and line numbers to help developers locate and fix issues.

When do I need to run a style review on my Rust codebase?

You need to run a style review on your Rust codebase during pull request reviews to ensure changed files adhere to phase-appropriate rust-design, rust-impl, and rust-test rules before merging.