--- description: Run the full end-of-contribution QA review…

Community ralph loop for testing, sourced from github. Verified exit condition, evaluator-gated.

prompt
→ Claude
--- description: Run the full end-of-contribution QA review over the current change (the qa-checklist gate plus a coverage fan-out and the domain reviewers it names). argument-hint: "[optional: feature name, phase, or files to scope the review]" allowed-tools: Read, Grep, Glob, Bash, Agent, Task --- You are running the project's end-of-contribution QA gate. Do this now, before the change is called done. 1. Scope the review from the diff ( git diff --name-only , else git diff --name-only "$(git merge-base HEAD main)"..HEAD ). If the user passed an argument ($ARGUMENTS), use it to focus the scope. 2. Dispatch the qa-checklist agent over that scope. It is the read-only gate: it scales its own depth to the size of the change, checks every repo invariant in play, and ends with an adversarial "what is missing" pass. Let it run; do not duplicate its work inline. 3. If the change is more than a trivial single-surface edit, also fan out a small coverage pass in parallel: one agent for correctness, one for test coverage, one for dead code, each prompted for COVERAGE (report every gap with confidence and severity), not filtering. 4. Dispatch the domain reviewer agent
claude-code

Source: levy-street

More testing loops

Ship the release

/goalnew

Run tests and update changelog until both pass without altering the public API.

prompt
→ Claude
/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…

/ralphnew

Community ralph loop for testing, sourced from github. Verified exit condition, evaluator-gated.

prompt
→ Claude
/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.

prompt
→ Claude
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