Sweep production errors to root cause
Trace actionable production errors to their root cause, verify the fix, open a PR, and stop cleanly when nothing needs action.
Use this when
Use this as a scheduled reliability pass when an agent can read production telemetry, trace failures into the repository, run the relevant tests, and prepare a reviewable fix.
How it runs
- Review the agreed production log window and group repeated symptoms into likely incidents.
- Separate actionable product errors from expected noise, transient upstream failures, and already-known issues.
- Trace each actionable error to a root cause, implement the smallest appropriate fix, and verify it with focused checks.
- Open a pull request for each verified fix. If the logs are clean, stop without making changes.
Done when
✓ Actionable production errors are fixed and verified. Finish with a pull request, or stop when no actionable errors are present.
Why it works
The loop converts passive log review into a closed reliability workflow. It requires a root cause, verified change, and review artifact instead of stopping at a list of errors.
Implementation note
Treat logs as sensitive production data. Do not copy credentials, tokens, personal information, or private payloads into prompts, pull requests, or chat messages.
More debugging loops
Memory leak hunt
Drive a suspected memory leak to ground: reproduce growth under a repeated workload, capture heap snapshots, and fix the retention until memory stays flat.
Keep asking for valid input
Loop until the user enters a number that passes your validation criteria.
Take a ticket to reviewer-ready
Turn a ticket or bug report into a proven root cause, a minimal patch, and a clean handoff a reviewer can trust.