check-code-quality

Automating Rust code quality checks involves orchestrating cargo check, build, clippy, test, and doc in a reliable sequence. This delivers consistent results and faster feedback before commits or PRs in local and CI workflows.

The best way to run cargo clippy and cargo test together is using an orchestrated workflow that sequences cargo check, build, clippy, test, and doc. This eliminates manual coordination and delivers consistent quality validation.

ICE recovery during Rust compilation automatically detects internal compiler errors and attempts recovery. It also performs toolchain escalation when needed to ensure the quality check workflow completes successfully.

Yes, you can run cargo doc and doctests as part of a CI pipeline by invoking a single orchestrated script. CI pipelines can trigger the full quality-check flow to validate code health before merging.

No additional dependencies are required to run these Rust linting checks. The workflow operates as a standalone script invoking standard cargo commands for typechecking, building, linting, testing, and documentation generation.

Rust quality check workflows can fail with internal compiler errors due to toolchain issues. This workflow includes automatic ICE recovery and toolchain escalation to handle these failures and retry the checks successfully.