Enforces failing-before-passing, red-green-refactor workflows for Rust projects.
npx skills add https://github.com/hwatkins/my-skills --skill rust-tdd-hwatkins
Please help me install this Agent Skill. Skill: rust-tdd Source: https://github.com/hwatkins/my-skills/tree/main/skills/rust-tdd Command: npx skills add https://github.com/hwatkins/my-skills --skill rust-tdd-hwatkins
Rust projects often suffer from insufficient test-driven development adoption, leading to delayed feedback and fragile code. This skill enforces test-driven development by requiring a failing test before implementation, ensuring code changes are driven by tests.
Write a failing test before implementing a new Rust feature and progressively refactor while keeping tests green.
High-intent search queries and answers about installing and using this skill.
You can enforce test-driven development in Rust by writing a failing test before implementing new code. This approach uses the red-green-refactor workflow to ensure code changes are driven by tests across features, bug fixes, and quality improvements.
The best way to organize unit and integration tests in a cargo workspace is following test organization patterns with guardrails for coverage and maintainability. This ensures tests drive design while keeping the Rust ecosystem structured.
The red-green-refactor workflow applies to Rust bug fixes by requiring a failing test that reproduces the bug first. You then implement the fix to make the test green and progressively refactor while keeping tests passing.
Yes, you can use this TDD approach for library crates, binary projects, and broader cargo workspaces. It applies across feature work and quality improvements, ensuring tests drive design and maintainability throughout the Rust ecosystem.
You should write a failing test before implementing a new Rust feature to enforce fail-fast feedback and prevent fragile code. This test-driven development practice ensures delayed feedback is minimized and code changes are explicitly validated.
No, this Rust TDD workflow does not require external testing frameworks or dependencies. It leverages standard Rust testing practices and cargo's built-in test organization patterns for unit and integration tests.
jamieadams-nerdScaffold a new Rust crate and register it in the workspace Cargo.toml.
ReinaMacCredyEnforce the Red-Green-Refactor cycle with failing tests before implementation.
dataroadincRun cargo test, fmt, and clippy checks on Rust projects.
DocaariGenerate executable tests from project specs and architecture diagrams.
