patch-sweep
Installation
SKILL.md
Patch Sweep — Fleet-Wide CVE Response
dependency-audit patches one project. This skill runs the response when a batch of advisories lands and you have 10, 40, or 100 apps across Vercel, Heroku, Render, Netlify, Fly, or Railway, split between a personal account, an agency org, and client repos.
Most of the real work in a sweep is outside npm audit: knowing which repo serves which domain, which branch production actually builds from, which production deploys no merge will ever replace, and which apps aren't affected at all. Get the map right first. Patching the wrong branch of the wrong repo is the most common way a sweep "finishes" with vulnerable code still live.
Cross-references:
dependency-audit— the per-project audit and fix procedure (in-range fixes, pnpm/yarn traps, duplicate singletons, engines floor, runtime pins). This skill calls it once per affected app.cloud-audit"PaaS" section — platform posture: stale manual deploys, broken git deploys, legacy projects, preview exposure, repo security defaults.scanner-pipeline— run osv-scanner / trivy once per repo instead of separate per-package-manager audits, and keep it running weekly afterward.finding-triage— rank the leftovers that can't be patched in range.security-comms— client and stakeholder notices, especially for client repos you can only PR.vuln-research— when an advisory's affected range or code path is unclear.personal-opsecC7 andagent-supply-chain-auditRT1 — the browsers agents download on one machine, and which extensions bring them.
Authorization — confirm before touching anything
Ask the user, and write the answers at the top of the board: