Menu
Assemble and file a GitHub issue on a repo, with a mandatory approval gate — never posts without showing the exact title+body first. Derived from gh-comment.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Development wisdom and workflow rules. NOT for project-specific conventions (those live in CLAUDE.md, edit via wisdom).
The `BUGS.md` open-issues queue — entry format, lifecycle, pruning to diary. NOT for the record-don't-fix policy (that's CLAUDE.md Bug Triage Protocol), NOT for resolved-bug history (use /diary), NOT for feature backlog (use TODO.md/specs).
Terminal demo GIF + MP4 recordings for READMEs and social (asciinema + agg + ffmpeg). NOT for general Makefile targets (use software) or GUI screenshots (use visual).
Go development. NOT for non-Go code (use rs, py, ts, tsx, or sh).
Humanize text: strip AI-isms and add real voice. NOT for drafting new copy (use writing).
Python development. NOT for shell scripting (use sh) or non-Python code.
| name | gh-issue |
| description | Assemble and file a GitHub issue on a repo, with a mandatory approval gate — never posts without showing the exact title+body first. Derived from gh-comment. |
| when_to_use | filing a bug report or issue on a GitHub repo, often a different repo than the current one (e.g. an upstream dependency), file an issue, open an issue, report a bug upstream |
| user-invocable | true |
Assemble a terse, actionable issue and file it — but ALWAYS show the exact content and get explicit approval BEFORE posting. Mirrors gh-comment's sign-off gate.
The issue often targets a DIFFERENT repo than the cwd (e.g. an upstream). Take
the owner/repo explicitly; never assume the current repo.
# current repo (only if the issue is about THIS project)
REPO=$(gh repo view --json nameWithOwner --jq .nameWithOwner)
# otherwise the user names it, e.g. REPO=marinade-finance/waypoint
If unsure which repo, ASK — do not guess a slug.
Short imperative sentence describing the defect (no type prefix).writing skill rules — no preamble, no padding, no "This issue…".
Include a copy-pasteable repro (curl/command) when there is one. Keep it to
what a maintainer needs to act; cut everything else.ALWAYS present the exact title + body to the user before posting. In Claude Code
use AskUserQuestion; elsewhere paste it in chat. NEVER run gh issue create
until the user explicitly approves the content and the target repo. Editing the
draft is expected — re-show after edits.
gh issue create --repo "$REPO" \
--title "<title>" \
--body "$(cat <<'EOF'
<body>
EOF
)" \
--label "<label>" # optional; omit if unsure
Return the issue URL that gh issue create prints.
--label for labels that exist (gh label list --repo "$REPO");
a non-existent label makes the command fail. Omit when unsure.gh is unauthenticated (gh auth status fails), do NOT attempt to post.
Show the approved title+body and the ready gh issue create command, and tell
the user to gh auth login (or run it themselves). Suggest ! gh auth login
in Claude Code so its output lands in the session.gh pr create/merge, gh release create, or git push.