What problem does it solve? Responding to a reported vulnerability requires strict confidentiality, a private development workflow, and perfectly timed publication so attackers get zero window between disclosure and patch availability. This Skill guides the entire GitHub Security Advisory response process for the Todero repository without leaking details publicly. ## Core Features & Use Cases - Confidential advisory handling: Fetches advisory details via the GitHub API and enforces rules against leaking vulnerability information in commits, branches, or public channels. - Private fork fix workflow: Creates a temporary private fork, develops and locally tests the patch (since CI does not run on private forks), and verifies the attack vector is closed. - Coordinated publication: Requests a CVE, credits the reporter, publishes the advisory, merges the fix, and cuts a security release simultaneously. - Use Case: A researcher reports a remote code execution vulnerability via GHSA. Use this Skill to acknowledge the reporter, patch the issue in a private fork, request a CVE, and publish the advisory and release in one coordinated step. ## Quick Start Handle the security advisory GHSA-x8hx-rhr2-9rf7 reported by a researcher, develop the fix in a private fork, and publish the advisory with a patched release.