deal-with-security-advisory

Manage GitHub Security Advisory response lifecycles with private forks and coordinated disclosure.

Updated May 27, 2026
One-click install
npx skills add https://github.com/bychrisr/now-company --skill deal-with-security-advisory-bychrisr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deal-with-security-advisory
Source: https://github.com/bychrisr/now-company/tree/main/.agents/skills/deal-with-security-advisory
Command: npx skills add https://github.com/bychrisr/now-company --skill deal-with-security-advisory-bychrisr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, confidential, and secure workflow for handling GitHub Security Advisories, ensuring that vulnerabilities are patched and disclosed without exposing sensitive details to attackers.

Core Features & Use Cases

  • Confidential Patching: Orchestrates the creation of private forks and secure development environments to prevent premature disclosure of vulnerability details.
  • Coordinated Disclosure: Manages the entire lifecycle of a security advisory, including reporter communication, CVE request, and synchronized publication.
  • Use Case: When a critical remote code execution vulnerability is reported, use this Skill to safely develop a fix in a private fork, coordinate with the reporter, and execute a zero-window release to protect users.

Quick Start

Execute the deal-with-security-advisory skill by providing the GitHub Security Advisory ID, reporter handle, severity, and a brief description of the vulnerability to initiate the secure patching process.

Frequently Asked Questions about deal-with-security-advisory

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

FAQPage Schema
How do I manage a GitHub Security Advisory and patch a vulnerability without premature disclosure?

To manage a GitHub Security Advisory securely, use a structured workflow that creates private forks for confidential patching and handles coordinated disclosure. This prevents exposing vulnerability details to attackers during remediation.

What is coordinated disclosure and how does it work with CVE assignment?

Coordinated disclosure manages the security advisory lifecycle, including reporter communication and CVE requests, to synchronize vulnerability publication. This ensures patches are released to users simultaneously with the public advisory.

How do I create a private fork to securely develop a vulnerability fix?

Creating a private fork for vulnerability remediation requires authenticated access via the GitHub CLI. The Skill orchestrates this secure development environment setup to isolate confidential patching from public repository access.

Do I need GitHub CLI authentication to handle security advisories and repository operations?

Yes, authenticated access to the GitHub CLI is required to perform repository operations and advisory management. This access enables the creation of private forks and the secure patching workflow needed for confidential vulnerability fixes.

What's the best way to execute a zero-window release for a critical remote code execution vulnerability?

Executing a zero-window release involves developing a fix in a private fork, coordinating with the reporter, and synchronizing the patch publication. This approach protects users by deploying the vulnerability fix simultaneously with the advisory.