- quality-streak-loop.md 42 lines · 1.9 KB
Quality Streak Loop
Loop Engineering — don't trust a single green run. Require a streak of clean passes to prove stability before stopping.
🎯 Goal
Exercise the product with realistic scenarios, fix every failure, and keep going until the suite passes N consecutive times — catching flakiness and intermittent bugs.
⏱️ Schedule
Suggested interval: 20m.
▶️ Run it
/loop 20m "Run the realistic scenario suite. Fix any failure you find, including flaky ones. Reset the streak counter on any failure. Continue until the suite passes 5 times in a row."🔁 Iteration steps
- Perceive — run the scenario suite via the
test-runnerhook. - Reason — analyze failures (real bug vs flake) with
/test-quality-analyzer. - Plan — fix the failure and harden the test.
- Act — implement the fix with
test-automator; reset the streak on any failure. - Observe — repeat; only stop after N consecutive clean runs.
🛑 Stopping condition
N consecutive passes (default 5) with zero failures or flakes.
🧩 Referenced components
agent:performance-testing/test-automator— fixes and hardens tests.hook:testing/test-runner— auto-runs the suite.command:testing/test-quality-analyzer— distinguishes real bugs from flakes.
💡 Example
The suite passes 4 times then a timing-dependent test flakes; the loop stabilizes it with a deterministic clock and restarts the streak until it hits 5 clean.
Scanned by NVIDIA SkillSpector
Automated static analysis (no LLM) · v2.12.0 · 2026-10-17
SkillSpector looks for patterns such as shell commands, credential access, network calls or unpinned dependencies. An observation is something worth reading in the files before you install, not a confirmed vulnerability. Components that run code locally, like hooks, MCP servers and security tooling, naturally show more of them.
No observations.
Learn more about NVIDIA SkillSpector.