Loop/Prompt Library / Security, data & reliability
🔁 Prove backups actually restore
Picks a real backup at random, restores it in a safe sandbox, and checks it works, again and again.
Use it when: You have backups but no proof they would save you in a real emergency.
🛑 Stops when: Every recovery scenario restores successfully [N] times in a row within your time and data-loss targets.
Copy this loop
For each recovery scenario in [list], pick a real backup at random and restore it from scratch in an isolated throwaway environment, using only the written recovery steps. Check the data is complete, the app can read and write, and how long it took and how much data was lost compared to [targets]. If something fails, fix one blocker, destroy the environment, and try again fresh. Stop when each scenario passes [3] times in a row, or after [10] attempts. Never overwrite production or expose the restored data. Destroy restored copies when done.
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 Eric Lott. 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.
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.
Fill in missing logs
Adds clear, tested log messages to every important part of the app so problems are easy to trace.