coding-guidelines

Codify Rust naming, formatting, and linting rules for code reviews.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mberetvas/dbt-migrator --skill coding-guidelines-mberetvas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-guidelines
Source: https://github.com/mberetvas/dbt-migrator/tree/main/.github/skills/coding-guidelines
Command: npx skills add https://github.com/mberetvas/dbt-migrator --skill coding-guidelines-mberetvas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Rust Coding Guidelines help developers align Rust code with established conventions, improving readability, maintainability, and safety by providing clear rules for naming, formatting, comments, clippy, rustfmt, and linting.

Core Features & Use Cases

  • Guide for consistent naming conventions across modules, types, and functions.
  • Standards for formatting, comments, clippy rules, and rustfmt compliance to reduce review time.
  • Use Case: when reviewing new Rust code or onboarding new contributors to ensure a uniform codebase.

Quick Start

Apply these guidelines when starting a new Rust project to ensure consistent naming, formatting, and linting.

Frequently Asked Questions about coding-guidelines

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

FAQPage Schema
How do I enforce consistent Rust naming and formatting rules across my project?

Apply established naming conventions, rustfmt formatting standards, and clippy linting rules during code reviews and project onboarding to ensure a uniform, readable Rust codebase.

What are the standard Rust clippy and rustfmt rules for code reviews?

Standard Rust code reviews codify rules for naming conventions, rustfmt compliance, and clippy linting to improve readability, maintainability, and safety while reducing review time.

Can I use these Rust coding guidelines for onboarding new contributors?

Yes, you can use these Rust coding guidelines when onboarding new contributors to ensure they follow uniform naming, formatting, comment, and linting rules across the project.

What's the best way to set up linting rules for a new Rust project?

The best way to set up linting for a new Rust project is to apply codified rules for clippy, rustfmt compliance, and naming conventions from the start, ensuring consistent style and safety.

Why do I need coding guidelines if I already use rustfmt and clippy?

You need coding guidelines alongside rustfmt and clippy to establish comprehensive rules for naming, comments, and code-review guidance that automated formatting and linting tools do not fully cover.