メニュー
Create a well-structured GitHub issue from a raw support thread or rough notes. Distills messy input into a clear issue with title, description, and repro steps, then files it and kicks off triage and solve.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Run a code review sub-agent
Post a DRAFT (pending) GitHub PR review made of separate inline review comments anchored to the diff, each with an AI-assisted disclosure and GitHub deep-link permalinks that render as code snippets. Use when the user asks to "add a draft review comment", "post review findings as separate comments", "leave inline review comments", or wants reviewer findings turned into a pending PR review with deep links to the code.
Create a GitHub issue describing the root problem behind current changes, then open a PR that references it
Convert a Marp markdown deck into a fully editable, on-brand PowerPoint (.pptx) built on a Google Slides template's native layouts, carrying speaker notes across, ready to upload to Google Slides. Use when someone wants a Marp deck "in Google Slides", "in the company template", or "as an editable branded deck" rather than rasterized slide images.
Commit, push, and open PR creation in the browser with an empty body for the human to fill in.
Reference for the workmux CLI that manages git worktrees and tmux windows as isolated development environments. Use when the user mentions workmux, worktrees, or parallel agent workflows.
| name | file-issue |
| description | Create a well-structured GitHub issue from a raw support thread or rough notes. Distills messy input into a clear issue with title, description, and repro steps, then files it and kicks off triage and solve. |
| argument-hint | [paste support thread or rough notes] |
| allowed-tools | Bash(gh *) Skill Read Grep Glob |
| disable-model-invocation | true |
Take the raw text provided in $ARGUMENTS (a support thread, Slack conversation, rough notes, etc.) and create a clean, well-structured GitHub issue from it.
The calling context should provide:
owner/repo) to file the issue inRead through the provided text and extract:
Ignore noise like greetings, tangents, "me too" replies, and troubleshooting attempts that didn't lead anywhere (unless they narrow down the root cause).
Compose a clear issue with:
Title: A concise, specific summary (not vague like "thing is broken"). Should describe the symptom or request.
Body: Structured markdown with the relevant sections below. Only include sections that are applicable:
<description of the problem or request, written clearly and concisely>
## Steps to Reproduce
1. ...
2. ...
## Expected Behavior
...
## Actual Behavior
...
## Environment
- ...
## Additional Context
<any relevant logs, error messages, or screenshots mentioned in the thread>
---
*Filed from support thread*
gh issue create -R <repo> --title "<title>" --body "<body>"
Report the created issue number and URL.
Run /triage <issue-number> then /solve <issue-number>, passing along any repo-specific context provided by the caller.