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
Approve a pull request using gh pr review --approve
Batch-triage open pull requests: list PRs with prs-awaiting-maintainer, review each with review-pr, then post-review-comments when there are merge-blocker findings, or create-scrap-issue for non-blocking findings and merge-pr when there are none. Use when the user wants to review and resolve a batch of PRs in one pass.
Clean up unnecessary local branches and prune stale remote-tracking branches
Clean git worktrees created by git-worktree-runner
Commit current changes, push to remote, and create or update a pull request. Use when the user wants to commit and create a PR, push changes and open a pull request, or ship their current work as a PR.
Analyze the differences between the current branch and origin/main, and summarize the current work progress
| name | understand-scrap-issues |
| description | Fetch the most recent maintainer-scrap issues (up to 3) and understand their content |
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).