plan-vulnerability-remediation

Plans dependency vulnerability remediation as a docs/epics epic with grouped child features.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/pnewsam/skills --skill plan-vulnerability-remediation-pnewsam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-vulnerability-remediation
Source: https://github.com/pnewsam/skills/tree/main/archive/plan-vulnerability-remediation
Command: npx skills add https://github.com/pnewsam/skills --skill plan-vulnerability-remediation-pnewsam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Dependency vulnerability alerts from Dependabot, audit tools, and security advisories arrive scattered and unverified, making it hard to turn them into safe, reviewable remediation work without duplicating existing PRs or mixing unrelated upgrades. ## Core Features & Use Cases - Finding Normalization and Verification: Collects CVE/GHSA findings from Dependabot alerts or audit tools (npm, pip, cargo, go, bundler) and checks manifests and lockfiles to confirm each vulnerability is still present. - Idempotent Grouping: Groups findings into coherent remediation units with stable group IDs, branch names, and PR markers, while detecting existing Dependabot/Renovate/manual PRs that already cover a finding. - Epic Generation: Creates or updates a standard vulnerability remediation epic in docs/epics/ with a remediation inventory table, success criteria, and child feature checklist. - Use Case: After a Dependabot alert flags a vulnerable lodash version, run this Skill to verify the lockfile state, check for an open fix PR, and produce an epic grouping all npm findings into focused remediation features. ## Quick Start Plan remediation for the current Dependabot alerts in this repository and create a vulnerability remediation epic under docs/epics.

Frequently Asked Questions about plan-vulnerability-remediation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan remediation for Dependabot alerts in a repository?▼

Gather alerts via the GitHub API, verify each finding against manifests and lockfiles, check open PRs for existing fixes, then group findings into remediation features recorded in a docs/epics vulnerability remediation epic.

What tools can I use to audit dependencies for vulnerabilities?▼

Supported audit sources include npm, pnpm, and yarn audit for JavaScript, pip-audit for Python, bundle audit for Ruby, cargo audit for Rust, and govulncheck for Go. Findings from these tools are normalized into advisory ID, package, fixed version, and severity.

Does this skill handle CodeQL or code scanning alerts?▼

No, CodeQL and SAST code scanning alerts are out of scope. Use the plan-code-scanning-remediation skill instead; this skill only covers dependency vulnerabilities in manifests and lockfiles.

Does planning vulnerability remediation change my lockfiles or dependencies?▼

No, the planning workflow is read-only. It never modifies manifests, lockfiles, source files, branches, or config; it only produces the remediation epic document for later execution.

How are vulnerability findings grouped into remediation PRs?▼

Findings are grouped when they share a safe coherent fix, such as the same package, manifest, or a single direct or transitive dependency update. Unrelated ecosystems, major upgrades, or migrations are kept in separate groups.