code-check

Validate and lint Rust and shell scripts with cargo check, clippy, and shellcheck.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/edgeandnode/ampup --skill code-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-check
Source: https://github.com/edgeandnode/ampup/tree/main/.agents/skills/code-check
Command: npx skills add https://github.com/edgeandnode/ampup --skill code-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate and lint code after changes to ensure clean, error-free Rust and shell scripts.

Core Features & Use Cases

  • Validate Rust code with cargo check and clippy to catch errors and warnings before merging.
  • Validate shell scripts with shellcheck to enforce scripting best practices.
  • Enforce a reliable pre-commit/pre-PR quality gate by running deterministic checks.

Quick Start

Run the code-check skill after editing code to automatically validate and lint your Rust and shell scripts.

Frequently Asked Questions about code-check

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

FAQPage Schema
How do I lint and validate Rust and shell scripts before a commit?

To validate and lint Rust and shell scripts before a commit, run checks that apply cargo check, clippy, and shellcheck to your codebase, ensuring your single-crate Rust workspace and shell scripts remain clean and error-free.

What is the best way to run clippy and shellcheck deterministically in a Rust project?

Running clippy and shellcheck deterministically is achieved by executing predefined just tasks for your Rust single-crate workspace. This enforces a reliable quality gate by running check-rs for Rust linting and check-sh for shell script validation.

Does shellcheck validation work alongside clippy linting in a single-crate workspace?

Yes, shellcheck validation works alongside clippy linting within a single-crate Rust workspace. The process sequentially executes shellcheck for shell scripts and clippy for Rust code to enforce scripting best practices and catch warnings.

Why do I need to run clippy and shellcheck before creating a pull request?

You need to run clippy and shellcheck before a pull request to enforce a reliable pre-PR quality gate. Validating and linting code after changes ensures clean, error-free Rust and shell scripts, preventing build failures or scripting issues from merging.

Can I use cargo check and clippy to catch warnings in a single-crate Rust workspace?

Yes, you can use cargo check and clippy to catch errors and warnings in a single-crate Rust workspace. These deterministic checks validate your Rust code compilation and enforce linting rules before commits or pull requests.