security-maintenance

Prioritize vulnerability advisories by project reachability and route fixes into tickets and releases.

1|Updated Sep 11, 2026
One-click install
npx skills add https://github.com/rebuildup/my-web-2026 --skill security-maintenance-rebuildup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-maintenance
Source: https://github.com/rebuildup/my-web-2026/tree/main/skills/security-maintenance
Command: npx skills add https://github.com/rebuildup/my-web-2026 --skill security-maintenance-rebuildup

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about security-maintenance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize security vulnerabilities beyond CVSS scores?

Evaluate exploitability, whether the vulnerable path is reachable in your project, external exposure, pre-auth access, data impact, and fix availability. Map these to project-specific priorities like P0 for actively exploited exposed flaws down to P3 for non-reachable defense-in-depth items.

What sources should I monitor for dependency security advisories?

Start with official framework and runtime security advisories, then official release notes, ecosystem advisory databases, and GitHub Security Advisories. Avoid relying on general news or social media as your security source of truth.

How do I handle a critical vulnerability in a transitive dependency?

First confirm whether the vulnerable code path is actually reachable in your project. If reachable and exposed, treat it as high priority with an isolated fix branch; if not reachable, schedule it as dependency hygiene work and document the reasoning in an Issue.

Should automated vulnerability scans block my CI pipeline?

Only if tuned to your project risk. Blocking on every scanner finding creates false-positive fatigue that destroys signal. Explicitly define which checks are blocking versus informational based on exposure and severity thresholds.

When should I re-evaluate my project's security posture?

Re-evaluate after framework or runtime major/minor upgrades, security policy changes, exposure changes, or adding new external services. These events alter reachability assumptions that prior prioritization decisions depended on.