Skill Detail

Shard, retry, and summarize Rust test runs with CI-friendly artifacts and failure isolation using cargo-nextest

Use cargo-nextest when an agent needs more reliable Rust test execution than cargo test, especially for sharding, retries, machine-readable output, and CI triage.

CI/CD IntegrationsMulti-Framework
CI/CD Integrations Multi-Framework Published
⭐ 2.9k GitHub stars ⬇ 9.8M/wk npm
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill shard-retry-and-summarize-rust-test-runs-with-ci-friendly-artifacts-and-failure-isolation-using-cargo-nextest Copy
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
Rust toolchain, Cargo workspace or crate, and CI or local shell access.
Install & setup
Install cargo-nextest with the Rust toolchain using the method documented by the project, add any nextest configuration your repository needs, then replace or supplement cargo test with cargo nextest run in local workflows or CI jobs.
Author
nextest contributors
Publisher
Community
Last updated
Apr 15, 2026
Quick brief

Tool: cargo-nextest. This skill is for agents that need to run Rust test suites with better scheduling, failure isolation, retries, and structured artifacts than the default test runner provides.

How it works

What this skill actually does

When to use it: invoke this in CI repair loops, flaky-test triage, or large Rust repositories where the agent needs to shard runs, rerun failures, or emit machine-readable results for downstream analysis. Using this skill is different from using the product normally because the operator workflow is specific: execute the suite under nextest, collect the artifacts, and turn failures into actionable repair or retry decisions.

Scope boundary: this is not a generic Rust testing listing and not a broad CI platform card. Its boundary is narrow: run and triage Rust tests with cargo-nextest when scheduling, retries, and failure summaries matter.