check

Run cargo fmt, clippy, and unit tests before committing.

3|2|Updated May 20, 2026
One-click install
npx skills add https://github.com/openkaiden/openshell-image-builder --skill check-openkaiden
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/openkaiden/openshell-image-builder/tree/main/.agents/skills/check
Command: npx skills add https://github.com/openkaiden/openshell-image-builder --skill check-openkaiden

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires cargo.

What problem does it solve?

This Skill eliminates the manual overhead of running repetitive code quality checks, ensuring your codebase remains clean and functional before every commit.

Core Features & Use Cases

  • Automated Formatting: Automatically runs and applies cargo fmt to ensure consistent code style.
  • Linting Enforcement: Uses cargo clippy with strict warning-as-error settings to catch potential bugs and anti-patterns.
  • Unit Test Validation: Executes the internal test suite to verify core logic integrity.
  • Use Case: Before pushing your changes to the repository, use this Skill to verify that your code meets all project standards and passes all unit tests without manual intervention.

Quick Start

Run the check skill to validate the current codebase and automatically fix any formatting issues found.

Frequently Asked Questions about check

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

FAQPage Schema
How do I automate pre-commit code quality checks for Rust?

Automate pre-commit code quality checks for Rust by running an automated suite that applies cargo fmt for formatting, enforces cargo clippy linting with warnings as errors, and executes unit tests to verify logic integrity before staging.

What is the best way to run cargo clippy and cargo fmt before a commit?

The best way to run cargo clippy and cargo fmt before a commit is using an automated check suite that enforces strict warning-as-error linting settings, applies formatting automatically, and validates unit tests without manual intervention.

Do I need cargo installed to run automated Rust testing and linting?

Yes, you need cargo installed and configured within your development environment to run automated Rust testing and linting, as the static analysis, formatting, and test execution rely entirely on cargo commands.

Why does my pre-commit workflow fail when cargo clippy finds warnings?

Your pre-commit workflow fails when cargo clippy finds warnings because the automated check suite uses strict warning-as-error settings to catch potential bugs and anti-patterns, blocking commits that do not adhere to project standards.

Can I automatically fix code formatting issues before pushing Rust code?

Yes, you can automatically fix code formatting issues before pushing Rust code by running the automated check suite, which executes and applies cargo fmt to ensure consistent code style across the codebase.