coding-guidelines

Define and enforce Rust coding guidelines for style and correctness.

3|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/0xharryriddle/codex-field-kit --skill coding-guidelines-0xharryriddle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-guidelines
Source: https://github.com/0xharryriddle/codex-field-kit/tree/main/archive/upstream/chasebuild-agent-skills/rust/skills/coding-guidelines
Command: npx skills add https://github.com/0xharryriddle/codex-field-kit --skill coding-guidelines-0xharryriddle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams apply a consistent Rust coding standard to reduce bugs, improve readability, and speed up code reviews.

Core Features & Use Cases

  • Naming conventions, formatting, and commenting guidelines aligned with Rust best practices.
  • Guidance on using Clippy and rustfmt within review checklists and educational materials.
  • Use Case: onboarding new Rust developers and standardizing reviews across multiple Rust projects.

Quick Start

Ask for Rust coding guidelines to audit or improve an existing Rust codebase.

Frequently Asked Questions about coding-guidelines

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

FAQPage Schema
What are standard Rust coding guidelines for naming conventions and formatting?

Standard Rust coding guidelines enforce specific naming conventions, formatting via rustfmt, and commenting rules to improve code style and readability across projects.

How do I use Clippy and rustfmt to enforce Rust code quality during reviews?

You can integrate Clippy and rustfmt into code review checklists to automatically identify lint violations and standardize formatting, ensuring consistent Rust code quality.

Can I apply a consistent Rust coding standard to onboard new developers?

Yes, applying a consistent Rust coding standard helps onboard new developers by providing clear rules for naming, lints, and common patterns to standardize reviews.

How do I audit an existing Rust codebase for coding style and correctness?

You audit an existing Rust codebase by applying defined coding guidelines to check naming, formatting, comments, and lints, which helps improve overall correctness and style.

What is the best way to standardize Rust code reviews across multiple projects?

The best way to standardize Rust code reviews is to enforce consistent guidelines for naming, formatting, and common patterns using Clippy and rustfmt across all projects.