dev_lint_check

Automate Rust static analysis with cargo clippy, fmt, and doc checks.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/maisonnat/axur-tool --skill dev-lint-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev_lint_check
Source: https://github.com/maisonnat/axur-tool/tree/main/.agent/skills/dev_lint_check
Command: npx skills add https://github.com/maisonnat/axur-tool --skill dev-lint-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Static analysis helps developers catch code quality issues, warnings, and formatting problems before runtime. This Skill enables automated static analysis of Rust projects using Clippy and rustfmt to detect warnings, formatting issues, and documentation gaps before code is merged.

Core Features & Use Cases

  • Clippy Analysis: cargo clippy --workspace -- -D warnings
  • Format Check: cargo fmt --check
  • Documentation Check (Optional): cargo doc --workspace --no-deps

Quick Start

Run cargo clippy --workspace -- -D warnings and cargo fmt --check to verify code quality before committing.

Frequently Asked Questions about dev_lint_check

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

FAQPage Schema
How do I automate Rust linting and formatting checks before committing code?

Automate Rust linting by running cargo clippy --workspace -- -D warnings and cargo fmt --check to catch code quality issues and formatting problems before merging.

Can I run clippy and cargo fmt checks together in a CI pipeline?

Yes, you can run clippy and cargo fmt checks together as configurable CI steps with clear exit codes to detect warnings, formatting issues, and documentation gaps.

What static analysis checks should I run for a Rust workspace?

For a Rust workspace, run static analysis checks using cargo clippy --workspace -- -D warnings, cargo fmt --check, and optionally cargo doc --workspace --no-deps.

Does this static analysis approach support documentation checks for Rust projects?

Yes, static analysis for Rust projects supports optional documentation checks by running cargo doc --workspace --no-deps to identify documentation gaps before code is merged.

Why should I treat clippy warnings as errors in my Rust project?

Treating clippy warnings as errors using the -D warnings flag enforces strict code quality standards by catching warnings, formatting issues, and documentation gaps before runtime.