Menu
Create a GitHub issue with detailed description, purpose, and appropriate labels
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
Draft a new release of the project.
Form an Agent Team of Implementer and Reviewer subagents to tackle the given task, looping implementation and review until the Reviewer reports zero high-or-above findings and no more than three mid findings.
Approve a pull request using gh pr review --approve
Babysit a Dependabot dependency-bump PR all the way to merge: verify the author is the genuine Dependabot bot, diagnose and resolve any CI failure (excluding or fixing a breaking bump when needed), get every check green, and merge. Use when the user wants to shepherd a Dependabot bump PR to merge.
Resolve every open issue one at a time: fact-check each with web research, close the ones that need no action, and run the `goal-pr` skill to fix, review, and merge the ones that do — repeating until no actionable issues remain.
Resolve every open maintainer-scrap issue one at a time: fact-check each with web research, close the ones that need no action, and run the `goal-pr` skill to fix, review, and merge the ones that do — repeating until no actionable scrap issues remain.
| name | create-issue |
| description | Create a GitHub issue with detailed description, purpose, and appropriate labels |
| targets | ["*"] |
Receive the issue topic from $ARGUMENTS or the user's description.
If the information is insufficient, ask the user to clarify the following:
Before writing the issue, investigate the relevant parts of the codebase to understand:
Important: All issue content (title, body, labels) must be written in English, regardless of the language used in the conversation with the user.
Create a well-structured issue with the following sections:
## Summary
A concise one-liner describing what this issue is about.
## Motivation / Purpose
Why this change is needed. Explain the problem, user impact, or improvement opportunity.
## Details
Detailed description of what needs to be done:
- Specific changes required
- Files or modules likely affected
- Acceptance criteria or expected behavior
## Additional Context
Any relevant links, screenshots, or references (if applicable).
First, get the available labels from the repository:
gh label list
Then choose appropriate labels from the existing repository labels based on the issue content. Also evaluate whether the issue is suitable for newcomers. If the contribution is straightforward (e.g., small scope, well-defined, minimal domain knowledge required), also assign the good first issue label if it exists in the repository.
gh issue create --title "<concise title>" --body "<drafted body>" --label "<label1>,<label2>,..."
Output the created issue URL and a summary of:
good first issue was applied and why (or why not)