What problem does it solve? When a CVE or vulnerability report lands, teams often patch blindly, bundle unrelated changes, or ship fixes without confirming the exposure is actually closed — creating false confidence while the system remains exploitable. ## Core Features & Use Cases - Exposure Verification: Confirms whether the codebase actually uses the vulnerable code path before patching anything, avoiding wasted effort on non-exposed CVEs. - Minimal Fix Discipline: Applies only the change that closes the vulnerability — no refactoring, no bundled changes — with standardized commit message formats for traceability. - Mandatory Verification & Urgent Deploy: Reproduces the attack vector before and after the fix, audits for the same pattern elsewhere, and deploys immediately with post-deploy production verification. - Use Case: A critical CVE is published for a dependency in your production API. Use this Skill to confirm your code path is exposed, upgrade to the patched version, verify the exploit no longer works, and deploy the same day. ## Quick Start A critical CVE was just published for one of our dependencies — walk me through confirming our exposure, applying the minimal fix, and deploying it today.
