Loop/Prompt Library / Security, data & reliability
🔁 Patch known security holes
Checks your software's building blocks for known security holes and fixes the ones that can actually hurt you first.
Use it when: A security scan shows high or critical vulnerabilities in your packages.
🛑 Stops when: No high or critical vulnerability you are exposed to is left without a fix or an approved decision.
Copy this loop
Scan [project]'s packages for known security vulnerabilities using current sources. If you cannot read the dependencies or advisories, tell me and stop. For each high or critical finding, check if our code actually uses the vulnerable part and if an attacker could reach it. Rank them by risk. Fix the riskiest reachable one with the smallest upgrade or patch, then re-run build, tests, and the scan. Keep it only if all pass. Repeat for at most [10] fixes. Ask before major upgrades or accepting a risk. Give me the full list with evidence.
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 hungtv27 (@hungtv27). Prompt rewritten in plain English by FixKit AI.
More loops like this
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.
Fill in missing logs
Adds clear, tested log messages to every important part of the app so problems are easy to trace.