Resolve Scrap Issues
Fetch recent maintainer-scrap issues, validate each with web research, then either...
Install
npx skills add dyoshikawa/rulesync --skill resolve-scrap-issues -g -a claude-code -y- Repository
- dyoshikawa/rulesync1.6k
- Category
- Git and review
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 1,804 tokens
- Runs scripts
- No, instructions only
What it does
Fetch recent maintainer-scrap issues, validate each with web research, then either close the ones that need no action or open a single consolidated pull request that resolves the ones that do
Fetch the newest scrap issues (GitHub issues labeled maintainer-scrap), understand each one, validate whether it is still a real and actionable problem using web research and codebase inspection, and then drive each issue to closure: close the issues that need no action, and resolve the actionable ones, bundling them into a single pull request when there is more than one.
This skill extends understand-scrap-issues: Steps 1, 3 are the same intake flow, and Steps 4 onward add validation and resolution.
Step 1: Fetch the Latest Scrap Issues
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.
Step 2: Gather Each Issue's Content
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.
Step 3: Understand and Summarize
For each scrap issue, explain the following based on its content:
- Topic: A one-line summary of what the scrap note is about.
- Background: The context, motivation, or problem the note captures and why it matters.
- Details / Findings: The specific observations, problems, or content recorded in the note.
- Proposed Solution / Next Steps: Any solution or actionable next step mentioned. If none is recorded, state explicitly that it is still undecided.
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.
