--- description: Run the full Rust quality gate…
Community ralph loop for testing, sourced from github. Verified exit condition, evaluator-gated.
--- description: Run the full Rust quality gate (fmt, clippy, tests) before shipping changes allowed-tools: Bash(cargo fmt: ), Bash(cargo clippy: ), Bash(cargo test: ) --- Run the IronClaw shipping checklist. This is the mandatory quality gate before any change is considered done. ## Steps 1. Format : Run cargo fmt to normalize formatting. 2. Lint : Run cargo clippy --all --benches --tests --examples --all-features and report any warnings or errors. ALL clippy warnings must be resolved before proceeding. 3. Test : Run cargo test --lib to execute the full library test suite. Report the total pass/fail count. 4. Summary : Report results for all three steps. If any step failed, list the specific errors and suggest fixes. Do NOT proceed past a failing step. If $ARGUMENTS is provided, treat it as a specific test filter and run cargo test --lib -- $ARGUMENTS instead of the full suite in step 3. The expected outcome for a clean ship is: - cargo fmt produces no changes - cargo clippy has zero warnings - All tests pass Note: Integration tests ( --test workspace integration ) require a PostgreSQL database and are expected to fail locally. Only report --lib
claude-code
More testing loops
Ship the release
Run tests and update changelog until both pass without altering the public API.
/goal ship the release --success "tests pass and changelog updated" --constraints "do not touch the public API" --mode ordered
testingmedium risk
/ralph-loop "fix all tests" --max-iterations 5 (iterates until…
Community ralph loop for testing, sourced from github. Verified exit condition, evaluator-gated.
/ralph-loop "fix all tests" --max-iterations 5 (iterates until passing
testingmedium risk
Trim what loads before first paint
Reduce the data downloaded before the first screen appears, with tests and screenshots guarding behavior and appearance.
Reduce the data [web app] downloads before its first screen appears. First record passing tests, mobile and desktop screenshots, and compressed transferred bytes—the data actually downloaded. Use the build report only to suggest candidates. Defer, compress, or remove one item, then rebuild and rerun every check. Keep it only if tests pass, screenshots are pixel-identical, and bytes decrease; otherwise revert. Stop when no safe candidate remains, progress stalls, or approval is needed. Return measurements, changes, and untested states.
testingmedium risk