skills.rest
bitan-del
bitan-delCOMMUNITY
Explore all skills by this author →
GitHub

godseye-ghsa-maintainer

Inspect, patch, validate, and publish GitHub Security Advisories with gh CLI.

4|2|Updated Mar 26, 2026
Search Tags:#workflow#security#github#patch#maintainer#advisories#ghsa
One-click install
npx skills add https://github.com/bitan-del/gods-eye --skill godseye-ghsa-maintainer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: godseye-ghsa-maintainer
Source: https://github.com/bitan-del/gods-eye/tree/main/.agents/skills/godseye-ghsa-maintainer
Command: npx skills add https://github.com/bitan-del/gods-eye --skill godseye-ghsa-maintainer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainer workflow for Gods Eye GitHub Security Advisories (GHSA). Use when Codex needs to inspect, patch, validate, or publish a repo advisory, verify private-fork state, prepare advisory Markdown or JSON payloads safely, handle GHSA API-specific publish constraints, or confirm advisory publish success.

Core Features & Use Cases

  • Fetch and inspect advisory state to confirm the current advisory and the latest published npm version, including linked private forks.
  • Verify private fork PRs are closed prior to publishing to ensure no open changes remain.
  • Prepare advisory Markdown and JSON payloads safely, using proper tooling to avoid unsafe string handling.
  • Apply PATCH calls in the correct sequence and publish by setting state to published, with post-publish verification.
  • Follow advisory guardrails and use when GHSA-specific publish constraints require careful orchestration.

Quick Start

Run the GHSA Maintainer workflow to inspect an advisory, generate safe patches, and publish when approved.

Frequently Asked Questions about godseye-ghsa-maintainer

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

FAQPage Schema
How do I publish a GitHub Security Advisory safely using the API?▼

To publish a GitHub Security Advisory safely, apply PATCH calls in sequence and set the state to published using the gh CLI. The workflow enforces guardrails and performs post-publish verification to confirm success.

What is the process to inspect a GHSA advisory and check linked private forks?▼

Inspecting a GHSA advisory involves fetching the current advisory state and the latest published npm version via shell tooling. This process confirms the active advisory details and verifies the status of linked private forks.

Do I need to close private fork PRs before publishing a repository advisory?▼

Yes, you must verify all private fork PRs are closed before publishing a repository advisory. This ensures no open changes remain and prevents conflicts during the GHSA API-driven publish workflow.

How do I generate safe Markdown and JSON payloads for GHSA patches?▼

Generate GHSA Markdown and JSON payloads safely using proper shell tooling and jq. This approach avoids unsafe string handling and ensures correct formatting for PATCH calls and subsequent publish workflows.

What tools are required to manage GitHub Security Advisories from inspect to publish?▼

Managing GitHub Security Advisories requires the gh CLI, jq, and standard shell tooling. These dependencies enable advisory inspection, patch sequencing, payload generation, and safe publish verification.

Related Skills

Explore More Software Engineering Skills→
vut08905vut08905

openclaw-ghsa-maintainer

Inspect GHSA advisory state, verify private forks, and generate Markdown and JSON payloads.

Community
Advanced
enclawedenclawed
2

enclawed-ghsa-maintainer

Inspect, patch, validate, and publish GitHub Security Advisories for Enclawed repositories.

Community
Advanced
jpoleyjpoley
50

patch-engineer

Validate security patch quality and regression risk for code changes.

Community
Advanced
bitwize-music-studiobitwize-music-studio
408

researchers-security

Compile source-backed security research briefs with citations from vendor advisories and CVE databases.

Official
Advanced