fix

# Vulnetix Fix Intelligence Skill ## Use when - You have a triaged CVE and want a concrete remediation proposal — not just "upgrade". - A version bump conflicts with peer-deps and you need to evaluate inline-as-first-party-code (Type A0) or patch (Type B). - You need to apply the fix, regenerate the lockfile, run a dry-run scan, and produce a CycloneDX SBOM in one workflow. - Generating rollback-safe manifest edits with `.vulnetix-backup` so you can revert. - Cross-checking registry fixes vs. distro patches vs. upstream source PRs. ## Don't use for - Just understanding the CVE — use `/vulnetix:vuln` or `/vulnetix:exploits`. - Verifying the fix landed — use `/vulnetix:verify-fix`. - Resolving a peer-dep conflict that blocks the fix — use `/vulnetix:dep-resolve`. - Building a multi-CVE upgrade plan — use the `@dep-upgrade-orchestrator` agent. ## 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 fetches fix intelligence for a vulnerability and proposes concrete, actionable remediation steps for the current repository. ## Output & Analysis Guidelines **Primary output...