run-linters

You can run linters for Markdown, YAML, TOML, Rust, and shell scripts using a single cargo-based runner. This unified linting workflow executes all style and correctness checks across the repository to ensure consistent code quality.

Yes, pre-commit hooks are fully supported to automate shell script and Rust linting. The framework integrates directly into pre-commit checks and CI pipelines to catch formatting and correctness issues early in the development lifecycle.

The best way to standardize code quality checks is wiring a unified linting framework with safe defaults. It applies consistent style and correctness rules across Markdown, YAML, TOML, Rust, and shell scripts.

Yes, the linter runner supports fast feedback for CI pipelines. It provides quick, targeted guidance for addressing lint errors across multiple languages and formats during local development and continuous integration.

To fix pre-commit linting errors missed by CI pipelines, run the full linting pipeline locally before committing changes. This applies all Markdown, YAML, TOML, Rust, and shell script checks to ensure code quality.

Yes, you need cargo to run the unified linters. The framework uses a single cargo-based linter runner to execute the suite of checks and per-linter commands across the repository.