What problem does it solve? Raw vulnerability feeds rank issues by CVSS score alone, which wastes effort on non-reachable flaws while missing exposures that actually threaten your project. This Skill turns advisory noise into a project-specific priority queue tied to real release decisions. ## Core Features & Use Cases - Reachability-Based Prioritization: Evaluates exploitability, external exposure, auth requirements, and fix availability to map advisories into P0-P3 project priorities instead of trusting CVSS blindly. - Structured Response Workflow: Guides the full cycle from advisory detection through Japanese GitHub Issue creation, isolated ticket branches, security verification, and release gating. - Automated Security Checks: Recommends dependency scanning, secret scanning, SAST, SBOM generation, and container scanning with explicit blocking/non-blocking policies to avoid false-positive fatigue. - Use Case: A GitHub Advisory flags a high-severity flaw in a transitive dependency. Use this Skill to confirm the vulnerable path is unreachable in your Worker, downgrade it to P3 hygiene work, and document the reasoning in an Issue instead of firefighting. ## Quick Start Review the latest security advisories for my framework and dependencies, assess their actual reachability in this project, and create prioritized GitHub Issues for anything that needs action.