remediation

# Vulnetix Remediation Plan Skill ## Use when - You need a structured playbook with prioritized actions, not just "upgrade to X". - CWE-specific guidance is needed (e.g. CWE-89 SQL injection across multiple packages). - Per-package-manager verification commands are required (`npm audit fix`, `pip-audit`, `go mod tidy --no-deps-check`, `cargo audit`). - Workaround effectiveness scores matter — partial mitigations need to be weighed against deferral. - Producing a remediation report for stakeholders who want the "what + why + how + verify" breakdown. ## Don't use for - Just applying a single fix — use `/vulnetix:fix`. - Verifying the fix worked — use `/vulnetix:verify-fix`. - Detection-only mitigation — use `/vulnetix:detection-rules`. ## Conventions This skill follows [`_lib/contract.md`](../_lib/contract.md): the Vulnetix CLI is auto-installed by hooks, `.vulnetix/capabilities.yaml` is always present, every `vulnetix vdb` call is piped through a verified `jq` filter from [`_lib/jq/`](../_lib/jq/), independent calls run in parallel as concurrent Bash tool calls, and trailing follow-ups are limited to one line. See the contract for output style, memory write rules, and cooldowns. This skill generates a comprehensive, context-aware remediation plan for a specific vulnerability using the VDB V2 remediation API. It auto-detects your repository's ecosystem, package manager, installed versions, container images, and OS to provide targeted fix guidance including registry upgr...