Executes the full pre-merge quality gate locally to ensure code meets CI standards before committing.
Install
mkdir -p .claude/skills/verify-rickymillar && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16759" && unzip -o skill.zip -d .claude/skills/verify-rickymillar && rm skill.zipInstalls to .claude/skills/verify-rickymillar
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Run the full CI quality gate locally before committingKey capabilities
- →Perform `cargo fmt --check` for format verification
- →Execute `cargo test` for individual crates
- →Run `cargo clippy` with `-D warnings` for linting
- →Conduct a demo job smoke test
- →Execute `viz` regression harness tests
How it works
The skill runs a sequence of commands including format checks, per-crate tests, clippy linting, a demo job smoke test, and viz regression tests to ensure the code meets CI quality gates.
Inputs & outputs
When to use verify
- →Format check
- →Run test suite
- →Run clippy
- →Smoke test
About this skill
/verify — Pre-Merge Quality Gate
Run these steps in order. They cover the same ground as .github/workflows/ci.yml, with the same feature flags — but per-crate rather than workspace-wide (see step 2), so the commands are not byte-identical to the workflow's.
Steps
1. Format check
cargo fmt --check
Fix: cargo fmt then review changes.
2. Test suite (per-crate — avoid workspace-wide)
This is the CI gate. Locally, run it only with the operator's go-ahead: the core line takes 30+ minutes. The usual local loop is the folder sentries, the focused crate tests and step 3.
cargo test -p rs_cam_core --features heavy-tests,research,test-support --no-fail-fast -- -q
cargo test -p rs_cam_cli -q
cargo test -p rs_cam_viz -q
cargo test -p rs_cam_mcp -q
Run per-crate — workspace-wide cargo test from the repo root can loop / swap-thrash on this repo (see operational guardrails).
--features heavy-tests on core is load-bearing: the 12 heaviest binaries are compiled only under that feature, and the gate must not lose those sentries. Do NOT reach for --include-ignored — #[ignore] here marks instruments and evidence runs (one family needs an externally installed validator), which are not gate material.
Fix: run failing test alone with cargo test -p <crate> <name> -- --nocapture.
3. Clippy (zero warnings)
cargo clippy --workspace --all-targets --features rs_cam_core/heavy-tests,rs_cam_core/research,rs_cam_core/test-support -- -D warnings
All three features belong here: without heavy-tests the 12 heavy binaries are never linted, without research the three finish/ research arms (conformal_spiral, direction_field, spiral_finish_compact) and their eight harnesses are never linted, and without test-support the eight harnesses that bind a maps/ or surface/ test door are never linted. Any of the three drifts silently.
Fix: address each warning — the project enforces -D warnings.
4. Demo job smoke test
mkdir -p demos && cargo run -p rs_cam_cli -- job fixtures/demo_job.toml
Fix: check fixtures/demo_job.toml and crates/rs_cam_cli/src/job.rs.
5. Viz regression harness
cargo test -p rs_cam_viz controller::tests::
cargo test -p rs_cam_viz compute::worker::tests::
Fix: check crates/rs_cam_viz/src/controller/tests.rs and compute/worker.rs.
All pass?
Ready to commit. All five steps must pass — this is what CI enforces on every PR.
When not to use it
- →When the user does not want to run the full CI quality gate locally
- →When only specific checks are needed, not the entire suite
Limitations
- →The skill is specific to Rust projects using `cargo`.
- →The skill requires all five steps to pass for a successful verification.
How it compares
This skill provides a standardized, automated local CI quality gate that mirrors the official CI, ensuring all checks pass before committing, unlike manual checks that might be incomplete.
Compared to similar skills
verify side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| verify (this skill) | 0 | 4mo | Review | Intermediate |
| pre_commit | 0 | 7mo | Review | Beginner |
| rust-tests-guidelines | 7 | 7mo | No flags | Beginner |
| check-rust-coverage | 5 | 7mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
pre_commit
pums974
Standardized pre-commit workflow for linting, formatting, and local quality gates.
rust-tests-guidelines
RediSearch
Guidelines for writing Rust tests.
check-rust-coverage
RediSearch
Check which Rust lines are not covered by Rust tests.
check-code-quality
r3bl-org
Run comprehensive Rust code quality checks including compilation, linting, documentation, and tests. Use after completing code changes and before creating commits.
lint
RediSearch
Check code quality and formatting before committing changes
run-clippy
r3bl-org
Run clippy linting, enforce comment punctuation rules, format code with cargo fmt, and verify module organization patterns. Use after code changes and before creating commits.