Dependency Update Backlog and Bot Alert Triage
Triage a pile of Dependabot or similar update pull requests and alerts into merge now, test first, batch later and ignore with reasons.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Help me triage the dependency update backlog in my repository [REPO_NAME]. I will paste a list of open update PRs or alerts with the package name, current version, proposed version, whether it is a patch, minor or major change, whether it is a direct or transitive dependency, any stated severity, and whether CI passed: [UPDATE_LIST]. Our application is [APP_TYPE] and the packages most critical to us are [CRITICAL_PACKAGES]. Sort every item into: Merge now, Test first, Batch with others, Plan as a project (major upgrade), Dismiss with documented reason, and Needs more information. Present a table with the columns Package, Change size, Severity as given, Group, Reason, and Check before merging. Give counts per group and the age distribution if dates are provided. Then recommend a cadence (for example weekly batch for patch updates) and a rule for who owns update PRs. Add a short note on grouping settings that reduce noise. Use only the data pasted. Do not invent vulnerability details, versions or changelog contents; tell me to read the release notes where it matters. Treat severity labels as given by the tool, not verified by you, and mark advice on security fixes [VERIFY] with whoever owns security for us. Do not merge or dismiss anything automatically. Bot configuration names differ by tool and plan, so mark them [VERIFY].
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.