verify

Run cargo check, test, clippy, and fmt across a Rust workspace.

Updated May 16, 2026
One-click install
npx skills add https://github.com/zeroclash-labs/zeroclash --skill verify-zeroclash-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/zeroclash-labs/zeroclash/tree/main/.claude/skills/verify
Command: npx skills add https://github.com/zeroclash-labs/zeroclash --skill verify-zeroclash-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you confidently verify that changes to the ZeroClash codebase still compile, pass tests, are clean under linting, and are properly formatted before you move forward.

Core Features & Use Cases

  • Workspace-wide verification: Runs cargo check, cargo test, cargo clippy, and cargo fmt -- --check across the entire workspace in a single sequence.
  • Early failure workflow: Stops at the first failing step to reduce time spent diagnosing downstream errors.
  • macOS GPUI patch validation: On macOS, checks whether a required GPUI patch was applied to prevent platform-specific build/runtime issues (helping with developer setup consistency).
  • Use case: After updating dependencies or refactoring modules, use this to ensure the full build + quality gate still holds across the project.

Quick Start

Run the verify workflow to check the workspace status after your changes.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I run a full Rust workspace verification suite after code changes?

To run a full Rust workspace verification, execute cargo check, cargo test, cargo clippy, and cargo fmt in sequence. This workflow stops early at the first failing step to quickly identify build, test, lint, or formatting issues.

Does cargo clippy and cargo fmt check work across the entire Rust workspace?

Yes, cargo clippy and cargo fmt checks run across the entire Rust workspace. The verification process applies these tools workspace-wide to ensure all modules and dependencies meet consistent linting and formatting standards.

What is the best way to verify Rust dependency updates before committing?

The best way to verify Rust dependency updates is running a CI-like validation sequence. This checks that the workspace still compiles, passes tests, lints cleanly under clippy, and maintains proper formatting after the changes.

Why does my Rust verification workflow stop early before running cargo fmt?

Your Rust verification workflow stops early because it is designed to halt at the first failing step. If cargo check, cargo test, or cargo clippy fails, the sequence stops to reduce time spent diagnosing downstream formatting errors.

How do I check for a required macOS GPUI patch during Rust build verification?

To check for a required macOS GPUI patch during Rust build verification, the workflow uses grep to detect patch presence. This prevents platform-specific build and runtime issues on macOS.

Can I use this cargo check and test sequence for CI-like validation?

Yes, you can use this cargo check and test sequence for CI-like validation. It applies continuous integration quality checks to ongoing development, dependency updates, and refactors across the full cargo workspace.