code-verifier

Run Rust verification suite with tests, coverage, formatting, clippy, and snippets.

1|Updated Sep 5, 2021
One-click install
npx skills add https://github.com/paruma/atcoder_rust --skill code-verifier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-verifier
Source: https://github.com/paruma/atcoder_rust/tree/main/.gemini/skills/code-verifier
Command: npx skills add https://github.com/paruma/atcoder_rust --skill code-verifier

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automatically validates edits to Rust libraries by running an integrated verification suite that enforces tests, coverage, formatting, linting, and snippet consistency.

Core Features & Use Cases

  • Unit tests & coverage: Executes module-specific tests and reports on pass/fail and coverage levels.
  • Code quality gates: Ensures code is formatted, clippy-warn-free, and snippets remain consistent.
  • Use Case: After updating src/mylib, trigger the verification to guarantee test success, full coverage, and clean code before merging.

Quick Start

Run the verification script for a module path such as data_structure::segtree_lib::lazy_segtree to perform the full quality gate.

Frequently Asked Questions about code-verifier

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

FAQPage Schema
How do I automate Rust code quality checks for unit tests, coverage, and linting?

Automated Rust code quality checks can be run by executing a unified verification suite that targets cargo test, cargo llvm-cov, cargo fmt, and cargo clippy for a specific module path. This generates clear PASS, WARN, or FAIL results.

What's the best way to verify Rust library edits before merging?

The best way to verify Rust library edits is triggering an integrated verification suite that enforces tests, coverage, formatting, clippy warnings, and snippet consistency. This guarantees test success and clean code before a merge.

Do I need the Rust toolchain and Python to run cargo clippy and snippet linting?

Yes, you need the Rust toolchain and Python installed to run the verification suite. These environments are required to execute cargo test, cargo llvm-cov, cargo fmt, cargo clippy, and the snippet_linter.

How does automated coverage assessment work with cargo llvm-cov for Rust modules?

Automated coverage assessment works by executing cargo llvm-cov alongside other quality checks for a given module path. It reports on pass and fail statuses while assessing coverage levels to ensure comprehensive library validation.

Can I run formatting and snippet integrity checks together with Rust unit tests?

Yes, you can run formatting and snippet integrity checks together with Rust unit tests. The unified verification suite executes cargo fmt, the snippet_linter, and cargo test simultaneously to report comprehensive module quality.

Why does my Rust code verification report a WARN result for clippy linting?

A Rust code verification suite reports a WARN result for clippy linting when cargo clippy detects code quality warnings in the targeted module path. The suite categorizes outcomes clearly into PASS, WARN, or FAIL statuses.