Rulesync create-scrap-issue
install
source · Clone the upstream repo
git clone https://github.com/dyoshikawa/rulesync
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/dyoshikawa/rulesync "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.rulesync/skills/create-scrap-issue" ~/.claude/skills/dyoshikawa-rulesync-create-scrap-issue && rm -rf "$T"
manifest:
.rulesync/skills/create-scrap-issue/SKILL.mdsource content
Create a single GitHub issue that consolidates all the content provided by the user.
Requirements
- Write the issue entirely in English.
- Always attach the
label to the issue.maintainer-scrap - Additionally, judge whether other labels are appropriate based on the content and attach them as needed. For example:
— if the content describes a defect or unexpected behaviorbug
— if the content proposes a new feature or improvementenhancement
— if the content relates to docs updatesdocumentation
— if the content discusses code restructuringrefactor- Use
to check available labels in the repository before attaching.gh label list
- 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
to create the issue.gh issue create
Workflow
- Review the content provided by the user.
- Organize and enrich it with background information and proposed solutions.
- Check available labels with
and determine which labels to attach in addition togh label list
.maintainer-scrap - Draft the issue body in the structure above.
- Create the issue with the appropriate labels using
.gh issue create --label maintainer-scrap --label <other-labels>