test

Run cargo fix, cargo fmt, and cargo test sequentially with stop-on-first-failure.

Updated Aug 23, 2026

Search Tags:#automation #testing #verification #rust #cargo #verify #ci

Ready to run

npx skills add https://github.com/cychen2021/claude-skills --skill test-cychen2021

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test
Source: https://github.com/cychen2021/claude-skills/tree/main/test
Command: npx skills add https://github.com/cychen2021/claude-skills --skill test-cychen2021

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the post-change verification workflow to ensure code changes pass formatting, compilation, and tests.

Core Features & Use Cases

Automates a three-step verification sequence (cargo fix, cargo fmt, cargo test) to ensure code changes compile and pass tests.
Stops immediately on failure and surfaces exact error output to speed debugging; produces a final pass/fail summary.
Use case: during a PR review, automatically validate new changes before merging to guard against broken builds.

Quick Start

Execute the automatic verification sequence to fix, format, and test your code changes and report the final results.

Frequently Asked Questions about test

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

FAQPage Schema

How do I automate Rust post-change verification with cargo fix, cargo fmt, and cargo test?▼

Automating Rust post-change verification involves running cargo fix, cargo fmt, and cargo test in sequence to validate code changes. This Skill executes all three steps deterministically, stopping on the first failure and providing a pass/fail summary.

Does this verification sequence stop on the first failing cargo test?▼

Yes, the verification sequence stops immediately on the first failing cargo test or compilation error. It surfaces the exact error output to speed up debugging before proceeding to subsequent steps.

Can I use this automated cargo verification for CI-like workflows in pull requests?▼

Yes, you can use this automated cargo verification for CI-like workflows to validate changes before merging. It guards against broken builds by producing a final pass/fail summary after checking formatting, compilation, and tests.

What is the best way to verify Rust code changes compile and pass tests before merging?▼

The best way to verify Rust code changes is an automated three-step sequence running cargo fix, cargo fmt, and cargo test in order. This ensures changes compile correctly, adhere to formatting standards, and pass all tests.

Do I need a specific Rust repository setup to run this automated cargo fix and test sequence?▼

You need a Rust codebase like the verifuzz project or similar repositories using cargo. The Skill applies to code changes requiring compilation, formatting, and test validation without additional dependencies.