메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Show off a library's REAL benchmark speed as a short thrilling terminal recording rendered to a mobile-friendly (tall+narrow) GIF — the bench appearing to run live, numbers landing, one headline holding. NOT for static bench tables or dated reports (those go in reports/), NOT for running the benchmark itself (use the lib's bench tool), NOT for UI/product video (use create video).
Install (or update) the Kronael toolkit into ~/.claude/ and bridge it into Codex. Copies skills, agents, hook scripts; merges Claude hook wiring; installs Codex hook wiring; installs the wisdom skill body as ~/.claude/CLAUDE.md; offers the standalone CLI tools (rig, udfix, clp, dockbox). First-time installs get an explained questionnaire. USE when the user says "install kronael", "install kronael tools", "install" (in this repo), or runs /kronael:install.
Install/update Kronael (bundle + CLI tools rig/udfix/clp/dockbox); bridge global/project CLAUDE.md, skills, and hooks into Codex.
Design specs in specs/ — numbered files, status frontmatter, index.md. NOT for in-flight tracking (use ship) or code/API docs (use readme).
Structure a project's docs by the question each file answers — README (what/why/how-to-start), ARCHITECTURE (how it's built), notes/ (why this design), compare/ (versus alternatives), facts/ (dated numbers) — plus a "how to read this" index and an anti-marketing discipline. Use when writing or auditing a project/crate/service README, ARCHITECTURE, or design docs; when docs are one mixed wall; or when someone asks for "good docs matching X quality". NOT for a single doc's prose polish (use writing), a design spec (use specs), or syncing docs after shipping (use readme).
Development wisdom and workflow rules. NOT for project-specific conventions (those live in CLAUDE.md, edit via wisdom).
| 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.