Menu
Fetch the most recent maintainer-scrap issues (up to 3) and understand their content
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 | understand-scrap-issues |
| description | Fetch the most recent maintainer-scrap issues (up to 3) and understand their content |
| targets | ["*"] |
Fetch the newest scrap issues (GitHub issues labeled maintainer-scrap) and understand what each one is about, so you can catch up on recently jotted-down notes before acting on them.
List the most recent open issues that carry the maintainer-scrap label. gh issue list returns issues in creation order (newest first), so limiting to 3 yields the 3 newest:
gh issue list --label maintainer-scrap --state open --limit 3 --json number,title,url,createdAt
If the result is empty, report that there are no open scrap issues and stop.
For each scrap issue returned, read both the body and the discussion. Run these in parallel across the issues where practical:
gh issue view <issue_number>
gh issue view <issue_number> --comments
If an issue references related pull requests, commits, or files that are needed to understand it, gather that context as well.
For each scrap issue, explain the following based on its content:
Keep each summary concise and focused. Present the issues in the order returned (newest first), with the issue number, title, and URL as a heading for each.
Use the language of the current conversation (follow the user's language).