Loop/Prompt Library / Security, data & reliability
🔁 Fill in missing logs
Adds clear, tested log messages to every important part of the app so problems are easy to trace.
Use it when: When something breaks, you cannot tell what happened from the logs.
🛑 Stops when: Every important path writes useful logs, and tests prove both success and failure cases log correctly.
Copy this loop
Review logging in [app]. List the important paths: user flows, service calls, background jobs, and failure cases. For each path missing good logs, add structured logs that say what happened, with no passwords or personal data. Add tests that check the logs appear for success and failure. Work through at most [15] paths. Stop when every important path is covered. Show me the list and what you added.
Review every change the agent makes before you keep it. Set a budget or round limit — the prompt includes one.
Idea from Forward Future's Loop Library · by Matthew Berman. Prompt rewritten in plain English by FixKit AI.
More loops like this
Patch known security holes
Checks your software's building blocks for known security holes and fixes the ones that can actually hurt you first.
Dependabot pull request triage
Reviews each automatic package-update pull request safely, fixes or merges the easy ones, and flags the risky ones for you.
Production error sweep
Reads your live app's error logs, finds a real problem, traces it to the cause, fixes it, and opens a pull request.
Prove backups actually restore
Picks a real backup at random, restores it in a safe sandbox, and checks it works, again and again.
Read-only reality check
Audits a project from its real code and settings, not assumptions, and grades each area with proof.
Clean up bad data
Removes records that do not belong in your live data and fixes the rule that let them in.