Menu
Triage a single GitHub issue. Read the issue, classify its type, add relevant labels, route to the correct repo if needed, and update project board status.
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
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 | triage |
| description | Triage a single GitHub issue. Read the issue, classify its type, add relevant labels, route to the correct repo if needed, and update project board status. |
| argument-hint | [issue-number] |
| allowed-tools | Bash(gh *) Read Grep Glob |
| disable-model-invocation | true |
Triage the issue specified by $ARGUMENTS. The calling context provides repo-specific details including the repo, issue type IDs, project board IDs, local repo paths, and routing rules.
gh issue view $ARGUMENTS -R <repo> --json id,number,title,body,comments,labels,assignees,url
Use the local repo paths provided by the calling context to search for relevant code. Read files, grep for keywords mentioned in the issue, and understand the area of the codebase involved.
Based on the issue content and codebase exploration, classify as one of the provided issue types (e.g. Bug, Feature, Task, Epic).
Guidelines:
Use the GraphQL updateIssue mutation with the issue's node ID and the appropriate type ID from the calling context:
gh api graphql -f query='mutation { updateIssue(input: {id: "<issue_node_id>", issueTypeId: "<type_id>"}) { issue { issueType { name } } } }'
Add labels that provide information beyond the issue type. Do NOT add labels that are redundant with the issue type (e.g. don't add a "bug" label if the issue type is Bug).
If routing rules are provided and the issue belongs in a different repo, transfer it:
gh issue transfer <issue-number> <destination-owner/repo> -R <source-owner/repo>
If project board details are provided, move the issue from "To triage" to "Backlog":
gh api graphql -f query='query { node(id: "<issue_node_id>") { ... on Issue { projectItems(first: 10) { nodes { id project { id } } } } } }'
gh api graphql -f query='mutation { updateProjectV2ItemFieldValue(input: {projectId: "<project_id>", itemId: "<item_id>", fieldId: "<status_field_id>", value: {singleSelectOptionId: "<backlog_option_id>"}}) { projectV2Item { id } } }'
Comment on the issue with a brief summary of the triage:
gh issue comment <issue-number> -R <repo> --body "<triage summary>"