Issue

Name: Issue
Author: godshiba

ASecurity

Register a bug, deferral, or known limitation as the next ISS-NNN in docs/registry/ISSUES.md with severity and an investigation path. Use when the user types /genesis:issue, says "log this bug/issue", "defer this", or when work uncovers a problem that will not be fixed in the current task in a GENESIS project.

2 stars
0 votes
0 copies
1 view
Added September 7, 2026

ai-agentsgit

Works with

Security analysis

A100/100

Scanned September 7, 2026

npx -y skills add godshiba/genesis --skill issue --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Issue?

Add the live security badge to your README. It updates with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/godshiba-issue/badge)](https://www.skillsdirectory.com/skills/godshiba-issue)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: issue
description: Register a bug, deferral, or known limitation as the next ISS-NNN in docs/registry/ISSUES.md with severity and an investigation path. Use when the user types /genesis:issue, says "log this bug/issue", "defer this", or when work uncovers a problem that will not be fixed in the current task in a GENESIS project.
---

# /genesis:issue — Register an Issue

Append one entry to the Open section of `docs/registry/ISSUES.md`. A problem
in a TODO comment is invisible; a problem with an ISS number is work.

## Steps

1. Determine the next sequential ID by scanning existing `ISS-` entries
   (including Resolved).
2. Pick severity: `high` (blocks or corrupts), `medium` (wrong but
   survivable), `deferred` (intentional, revisit later). If unclear from
   context, default to `medium` and say so.
3. Write the entry in the file's format: title, severity, registered date
   (today's real date), context with file paths, and a concrete investigation
   path — the first commands or files whoever picks this up should look at.
4. **GitHub mirror — only when every condition holds, else skip silently.**
   Mirror to GitHub *only* if all of these are true: `GENESIS_GITHUB` is `on`
   (default `off` — GENESIS never touches GitHub unless opted in via
   `/genesis:config`); a `github.com` remote exists; `gh` is installed
   (`command -v gh`); and `gh auth status` succeeds. When all hold, run
   `gh issue create --title "ISS-NNN: <title>"` with a body pointing at the
   canonical ISSUES.md entry, then back-fill the `**GitHub:** [#N](url)` line.
   If any condition is missing, the issue stays local — skip without a word,
   never a blocker, never a prompt. `gh` is a separate CLI that acts on
   GitHub's servers; treat it as opt-in, capability-checked, and side-effecting.
5. If the code contains a related TODO/FIXME, rewrite it to cite the ID:
   `// TODO(ISS-NNN): ...`.
6. Confirm in one line: `ISS-NNN registered (severity) — <title>`.

Resolving (when asked): move the entry under Resolved with a dated note —
never delete — and, if GitHub mirroring is enabled and a mirror exists, close
it in the same commit.