create-scrap-issue

Consolidate user-provided content into a GitHub issue labeled maintainer-scrap.

1.3k|142|Updated Jun 18, 2025
One-click install
npx skills add https://github.com/dyoshikawa/rulesync --skill create-scrap-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-scrap-issue
Source: https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/create-scrap-issue
Command: npx skills add https://github.com/dyoshikawa/rulesync --skill create-scrap-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill consolidates user-provided content into a single GitHub issue labeled maintainer-scrap, saving time and preserving context for future reference.

Core Features & Use Cases

  • Consolidates notes, observations, and context into one issue with structured sections for background, details, and solution.
  • Automatically applies the maintainer-scrap label and suggests additional labels based on content.
  • Supports creating scrap issues for knowledge capture, decision logs, or post-mortems.

Quick Start

Create a new GitHub issue containing all user-provided content with the maintainer-scrap label.

Frequently Asked Questions about create-scrap-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I consolidate notes and context into a single GitHub issue for post-mortem preparation?

This Skill consolidates notes into a GitHub issue by structuring user-provided content into background, details, and proposed solution sections, applying the maintainer-scrap label for post-mortem preparation and knowledge capture.

What is a scrap issue in GitHub and when should I use it?

A scrap issue is a GitHub issue labeled maintainer-scrap used to preserve observations and context. Use it for decision logs, post-mortems, and knowledge capture to ensure findings remain accessible for future reference.

Can I automatically apply labels to a GitHub issue based on its content?

Yes, you can automatically apply labels based on content. This Skill applies the required maintainer-scrap label and suggests additional labels by analyzing the provided notes and context during issue creation.

Does this GitHub issue automation work without additional dependencies?

Yes, this GitHub issue automation operates without additional dependencies. It requires no external components or modules to consolidate notes and apply the maintainer-scrap label to the generated issue.

What is the best way to structure a decision log in GitHub?

The best way to structure a decision log in GitHub is using a scrap issue with dedicated sections for background, details, and proposed solutions, ensuring all context is consolidated for future reference.