Loop 004

The production error sweep

A scheduled production-log workflow that traces actionable errors to root causes, verifies fixes, opens a pull request, and stops cleanly when no action is needed.

Ready-to-use prompt

Copy the loop

Review our production logs for errors. If you find an actionable issue, trace it to its root cause, fix it, verify the fix, and open a pull request. If no actionable errors are present, stop without making changes.

Verify / stop

Actionable production errors are fixed and verified.

Finish with a pull request, or stop when no actionable errors are present.

Context and guidanceWhen to use it, steps, safety notes, and related loops
Published
Updated

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 to run it

  1. Review the agreed production log window and group repeated symptoms into likely incidents.
  2. Separate actionable product errors from expected noise, transient upstream failures, and already-known issues.
  3. Trace each actionable error to a root cause, implement the smallest appropriate fix, and verify it with focused checks.
  4. Open a pull request for each verified fix. If the logs are clean, stop without making changes.

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.