create-scrap-issue — Claude Code skill: what it does, how to install
This skill turns notes and findings into one GitHub issue with context, details, and next steps. Use it when you want to keep project scraps for later.
npx skills add dyoshikawa/rulesync --skill create-scrap-issue -a claude-codeWhat create-scrap-issue does
create-scrap-issue takes everything supplied by the user and turns it into a single GitHub issue. The issue uses three sections: Background, Details, and Solution / Next Steps. It also creates a descriptive title and always applies the maintainer-scrap label.
Before opening the issue, the skill checks repository labels with gh label list and can add labels such as bug, enhancement, documentation, or refactor when the content calls for them. It creates the issue through gh issue create. The resulting issue is written in English, including when the source notes are in another language.
What it helps with
- turn scattered notes into one GitHub issue
- preserve context around a finding for later review
- outline a solution and actionable next steps
- apply the
maintainer-scraplabel to an issue - choose extra labels from the issue content
Example prompts for the agent
- Create a scrap issue from these notes about the failed build and the checks I already ran.
- Turn this finding into one GitHub issue with background, details, and next steps.
- Save this investigation as a scrap issue and add any suitable labels.
How to install create-scrap-issue
1Skills CLI (Vercel)
npx skills add dyoshikawa/rulesync --skill create-scrap-issue -a claude-code2Manually: put the files in place
~/.claude/skills/create-scrap-issue/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/create-scrap-issue/
1Skills CLI (Vercel)
npx skills add dyoshikawa/rulesync --skill create-scrap-issue -a codex2Manually: put the files in place
.agents/skills/create-scrap-issue/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add dyoshikawa/rulesync --skill create-scrap-issue -a cursor2Manually: put the files in place
.cursor/skills/create-scrap-issue/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install dyoshikawa/rulesync create-scrap-issue2Manually: put the files in place
.github/skills/create-scrap-issue/SKILL.md1Skills CLI (Vercel)
npx skills add dyoshikawa/rulesync --skill create-scrap-issue -a gemini-cli2Platform CLI
gemini skills install https://github.com/dyoshikawa/rulesync --path .rulesync/skills/create-scrap-issueManually: put the files in place
.devin/skills/create-scrap-issue/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add dyoshikawa/rulesync --skill create-scrap-issue -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about create-scrap-issue
How do I install create-scrap-issue in Claude Code?
Run npx skills add dyoshikawa/rulesync --skill create-scrap-issue -a claude-code. The skill file will be placed at ~/.claude/skills/create-scrap-issue/SKILL.md.
What does create-scrap-issue do?
It converts supplied notes into one GitHub issue with Background, Details, and Solution / Next Steps sections. The issue always receives maintainer-scrap, while other labels are chosen from the content.
What language does the skill use for the issue?
The issue is written entirely in English. The skill checks labels with gh label list and creates the issue with gh issue create.
Source text
SKILL.md · MIT
--- name: create-scrap-issue description: >- Create a GitHub issue that consolidates passed content into a single scrap issue with background context and solution details, labeled as maintainer-scrap. Use when the user wants to create a scrap issue, jot down notes as a GitHub issue, or save findings for later. targets: - "*" --- Create a single GitHub issue that consolidates all the content provided by the user. ## Requirements - Write the issue entirely in English. - Always attach the `maintainer-scrap` label to the issue. - Additionally, judge whether other labels are appropriate based on the content and attach them as needed. For example: - `bug` — if the content describes a defect or unexpected behavior - `enhancement` — if the content proposes a new feature or improvement - `documentation` — if the content relates to docs updates - `refactor` — if the content discusses code restructuring - Use `gh label list` to check available labels in the repository before attaching. - Structure the issue so it is easy to understand even when revisited later: - **Background**: Describe the context, motivation, and why this matters. - **Details**: Include the specific content, observations, or problems passed by the user. - **Solution / Next Steps**: Propose a solution or outline actionable next steps. - Use a clear, descriptive title that summarizes the scrap topic. - Use `gh issue create` to create the issue. ## Workflow 1. Review the content provided by the user. 2. Organize and enrich it with background information and proposed solutions. 3. Check available labels with `gh label list` and determine which labels to attach in addition to `maintainer-scrap`. 4. Draft the issue body in the structure above. 5. Create the issue with the appropriate labels using `gh issue create --label maintainer-scrap --label <other-labels>`.
© dyoshikawa · MIT · dyoshikawa/rulesync