Files
wehub-resource-sync bb5c75ce05
Component Security Validation / Security Audit (push) Has been cancelled
Deploy to Cloudflare Pages / deploy (push) Has been cancelled
chore: import upstream snapshot with attribution
2026-07-13 12:38:58 +08:00

1 line
2.1 KiB
JSON
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
{"content": "---\nname: production-error-sweep-loop\ndescription: Triages production errors, finds the root cause, ships a verified fix, and repeats until the error budget is clean.\ncategory: engineering\ninterval: 15m\nstop-condition: No unresolved high-severity production errors remain and each fix is verified in tests.\ncomponents: [agent:expert-advisors/debug, agent:security/incident-responder, command:git-workflow/create-pr]\ntags: [debugging, incidents, reliability, loop]\n---\n\n# Production Error Sweep Loop\n\n> **Loop Engineering** — keep an autonomous responder working the error queue, one root cause at a time, until production is quiet.\n\n## 🎯 Goal\nContinuously pull the top production error, find its **root cause** (not just the symptom), ship a tested fix, and verify the error stops recurring.\n\n## ⏱️ Schedule\nSuggested interval: `15m` (or trigger on new error alerts).\n\n## ▶️ Run it\n```\n/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.\"\n```\n\n## 🔁 Iteration steps\n1. **Perceive** — read the top error by impact (frequency × severity).\n2. **Reason** — reproduce and trace to the true root cause with the `debug` agent.\n3. **Plan** — design a minimal fix plus a regression test that fails first.\n4. **Act** — implement the fix; the `incident-responder` agent documents impact and mitigation.\n5. **Observe** — confirm the regression test passes, then open a PR with `/create-pr`.\n\n## 🛑 Stopping condition\nThe high-severity error queue is empty and every fix is covered by a passing regression test.\n\n## 🧩 Referenced components\n- `agent:expert-advisors/debug` — root-cause analysis.\n- `agent:security/incident-responder` — impact assessment and mitigation notes.\n- `command:git-workflow/create-pr` — ships each fix for review.\n\n## 💡 Example\nA 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`.\n"}