OpenParable
Skip to content
← Back to skills

Ghsa

DevOps & Security
ghsa

Ghsa is an Agent Skill for devops & security published in the gogs/gogs repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Analyze and help fix a GitHub Security Advisory (GHSA) in this repository. Use when the user types `/ghsa <id>` or asks to triage, verify, or patch a reported GHSA.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/gogs/gogs/blob/HEAD/.agents/skills/ghsa/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/ghsa, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

GHSA

Analyze and help fix the GitHub Security Advisory (GHSA) provided as the skill argument.

Steps:

  1. Fetch the GHSA page using gh api repos/gogs/gogs/security-advisories and understand the vulnerability details (description, severity, affected versions, CWE).
  2. Verify the reported vulnerability actually exists, and why.
  3. Identify the affected code in this repository.
  4. Propose a fix with a clear explanation of the root cause and how the fix addresses it. Check for prior art in the codebase to stay consistent with existing patterns.
  5. Implement the fix. Only add tests when there is something meaningful to test at our layer.
  6. Run all the usual build and test commands.
  7. Add it to CHANGELOG.md with a placeholder for the PR link.
  8. Create a branch named after the GHSA ID, commit, and push.
  9. Create a pull request with a proper title and description, do not reveal too much detail and link the GHSA.
  10. If a changelog entry was added, update it with the PR link, then commit and push again.