workspace-testslisted

Run cargo test --workspace across a list of Rust workspaces, failing fast and reporting which repo broke. Surfaces sibling-workspace regressions that single-repo hygiene cycles miss. Use when the user says "verify cross-repo tests", "run hygiene", "anything broken in sibling workspaces?", or as part of a /loop hygiene priority.
thepictishbeast/claude-tools · ★ 0 · Testing & QA · score 68

Install: claude install-skill thepictishbeast/claude-tools

# /workspace-tests — cargo test across N Rust workspaces Walks a configured list of in-scope Rust workspaces and runs `cargo test --workspace` against each. Fails fast (stops at first red workspace) by default; `--continue-on-error` runs the full set. Reports total + per-repo pass/fail counts. ## Why this exists Surfaced 2026-05-20 from PlausiDen-Forge #303: an opportunistic hygiene cycle that ran `cargo test --workspace` only on the currently-active repo silently missed a real E0063 in Loom (`CmsSection::Form` scaffold missing `style` field). Cross-repo discovery only happened when the next agent ran `cargo fmt` and hit the compile error. Real failure mode: a substrate-wide field addition lands in one crate but the consumer-side scaffolds in sibling repos don't update. Tests still pass in the producer crate; consumer crate breaks at HEAD. Without explicit cross-repo coverage, hours of "green builds" accumulate before the gap surfaces. ## Steps ### 1. Read the workspace list Default in-scope set (PlausiDen substrate): ``` /home/paul/projects/PlausiDen-Forge /home/paul/projects/PlausiDen-Loom /home/paul/projects/PlausiDen-Crawler /home/paul/projects/Crucible ``` LFI repos (PlausiDen-LFI, Forge-LFI) are excluded by default — they have a dedicated Claude instance per memory `feedback_lfi_out_of_scope_for_this_instance`. Add `--include-lfi` to override. User can override the set via: - `$WORKSPACE_TESTS_REPOS` env (colon-separated absolute paths) - `~/.config/workspace-