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.
Best use case
create-scrap-issue is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using create-scrap-issue should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/create-scrap-issue/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How create-scrap-issue Compares
| Feature / Agent | create-scrap-issue | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
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>`.
Related Skills
create-issue
Create a GitHub issue with detailed description, purpose, and appropriate labels
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
security-scan-diff
Scan for malicious code in git diff between a tag/commit and HEAD
release-dry-run
Dry run for release: summarize changes since last release and suggest version bump.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
git-worktree-runner
Manages git worktrees using git-worktree-runner (gtr). Use when the user needs to create, list, remove, or navigate worktrees with `git gtr` commands, open editors or AI tools in worktrees, manage parallel development branches, or check out GitHub PRs (including from forks) into worktrees.
draft-release
Draft a new release of the project.
review-pr
Review a pull request for code quality and security issues. Use when the user wants to review a PR, check PR code changes, or audit a pull request. Triggers on: "review PR", "review pull request", "check this PR", "/review-pr".
review-and-comments
Review a PR for code quality and security issues, then post review comments on it. Runs review-pr followed by post-review-comments sequentially.
rebase-latest-main
Fetch latest origin/main and rebase it onto the current branch, resolving conflicts if necessary. Use when the user wants to rebase on main, update their branch with latest main, or sync with upstream.
post-review-comments
Post line-level review comments and an overall review comment on a PR in English with a natural, concise writing style