Individual skill

create-scrap-issue

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.

.rulesync/skills/create-scrap-issue/SKILL.md

Read pinned source

Source commit 2d5bbc81aa01346601fcb2d1e18c71af07a02728

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,591
Repository last updated: Nov 7, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

ai Repository topic
ai-agents Repository topic
ai-coding Repository topic
llm Repository topic
mcp Repository topic
rules Repository topic
skills Repository topic
writing Derived category
productivity Derived category
productivity-notes Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 1,886 bytes

Read excerpt


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.