Agent skill

resolve-scrap-issues

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

dyoshikawa1,265★ · +16/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add dyoshikawa/rulesync --skill resolve-scrap-issues --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Path: .rulesync/skills/resolve-scrap-issues/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,285 · +20 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

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: ```bash 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: ```bash gh issue view <issue_number> gh issue view <issue_number> --comments ``` If an issue references related pull requ

What's inside
Steps it walks through
  1. Step 1: Fetch the Latest Scrap Issues
  2. Step 2: Gather Each Issue's Content
  3. Step 3: Understand and Summarize
  4. Step 4: Validate Each Issue
  5. Step 5: Close the Issues That Need No Action
  6. Step 6: Resolve the Issues That Need Action
  7. 6a. Plan the change
  8. 6b. Branch
  9. 6c. Implement
  10. 6d. Verify
  11. 6e. Commit, push, and open ONE consolidated PR
  12. Step 7: Report Result
Commands it runs
gh issue list --label maintainer-scrap --state open --limit 3 --json number,title,url,createdAt
gh issue view <issue_number>
gh issue view <issue_number> --comments
gh issue close <issue_number> --comment "<reason with evidence>"
pnpm cicheck
git add .
git commit -m "<message>"
git push -u origin <branch-name>
gh pr create --title "<title>" --body "<description>"
More from rulesync
All skills →
About this skill
What does the resolve-scrap-issues skill do?

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

How do I install it?

Run `npx skills add dyoshikawa/rulesync --skill resolve-scrap-issues --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From dyoshikawa/rulesync, a repository with 1,285 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going