2.1 KiB
2.1 KiB
name, description, category, interval, stop-condition, components, tags
| name | description | category | interval | stop-condition | components | tags | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| production-error-sweep-loop | Triages production errors, finds the root cause, ships a verified fix, and repeats until the error budget is clean. | engineering | 15m | No unresolved high-severity production errors remain and each fix is verified in tests. |
|
|
Production Error Sweep Loop
Loop Engineering — keep an autonomous responder working the error queue, one root cause at a time, until production is quiet.
🎯 Goal
Continuously pull the top production error, find its root cause (not just the symptom), ship a tested fix, and verify the error stops recurring.
⏱️ Schedule
Suggested interval: 15m (or trigger on new error alerts).
▶️ Run it
/loop 15m "Take the highest-impact unresolved production error. Reproduce it, find the root cause, write a regression test, fix it, and open a PR. Continue until no high-severity errors remain."
🔁 Iteration steps
- Perceive — read the top error by impact (frequency × severity).
- Reason — reproduce and trace to the true root cause with the
debugagent. - Plan — design a minimal fix plus a regression test that fails first.
- Act — implement the fix; the
incident-responderagent documents impact and mitigation. - Observe — confirm the regression test passes, then open a PR with
/create-pr.
🛑 Stopping condition
The high-severity error queue is empty and every fix is covered by a passing regression test.
🧩 Referenced components
agent:expert-advisors/debug— root-cause analysis.agent:security/incident-responder— impact assessment and mitigation notes.command:git-workflow/create-pr— ships each fix for review.
💡 Example
A recurring null-pointer crash is traced to an unvalidated webhook payload; the loop adds a failing regression test, fixes the validation, verifies, and opens fix: validate webhook payload before parse.