Source profileQuality 68/100
dyoshikawa/rulesync/.rulesync/skills/understand-scrap-issues/SKILL.md
understand-scrap-issues
Fetch the most recent maintainer-scrap issues (up to 3) and understand their content
- Source repository stars
- 1,263
- Declared platforms
- 0
- Static risk flags
- 0
- Last source update
- 2026-07-28
- Source checked
- 2026-07-28
Decision brief
What it does—and where it fits
List the most recent open issues that carry the maintainer-scrap label. gh issue list returns issues in creation order (newest first), so limiting to 3 yields the 3 newest:
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
Source-detected install commandSource
npx skills add https://github.com/dyoshikawa/rulesync --skill ".rulesync/skills/understand-scrap-issues"Safe inspection promptEditorial
Inspect the Agent Skill "understand-scrap-issues" from https://github.com/dyoshikawa/rulesync/blob/310b711fbe8cffc14debb276ade8a384c2b89083/.rulesync/skills/understand-scrap-issues/SKILL.md at commit 310b711fbe8cffc14debb276ade8a384c2b89083. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
Step 1: Fetch the Latest Scrap Issues
List the most recent open issues that carry the maintainer-scrap label. gh issue list returns issues in creation order (newest first), so limiting to 3 yields the 3 newest:
List the most recent open issues that carry the maintainer-scrap label. gh issue list returns issues in creation order (newest first), so limiting to 3 yields the 3 newest:If the result is empty, report that there are no open scrap issues and stop. - 02
Step 2: Gather Each Issue's Content
For each scrap issue returned, read both the body and the discussion. Run these in parallel across the issues where practical:
For each scrap issue returned, read both the body and the discussion. Run these in parallel across the issues where practical:If an issue references related pull requests, commits, or files that are needed to understand it, gather that context as well. - 03
Step 3: Understand and Summarize
For each scrap issue, explain the following based on its content:
Topic: A one-line summary of what the scrap note is about.Background: The context, motivation, or problem the note captures and why it matters.Details / Findings: The specific observations, problems, or content recorded in the note.
Permission review
Static risk signals and limitations
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
Why each signal appears
EvidenceSourceComputedTestedEditorial
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 68/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 1,263 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- dyoshikawa/rulesync
- Skill path
- .rulesync/skills/understand-scrap-issues/SKILL.md
- Commit
- 310b711fbe8cffc14debb276ade8a384c2b89083
- License
- MIT
- Collected
- 2026-07-28
- Default branch
- main
View the original SKILL.md
Fetch the newest scrap issues (GitHub issues labeled maintainer-scrap) and understand what each one is about, so you can catch up on recently jotted-down notes before acting on them.
Step 1: Fetch the Latest Scrap Issues
List the most recent open issues that carry the maintainer-scrap label. gh issue list returns issues in creation order (newest first), so limiting to 3 yields the 3 newest:
gh issue list --label maintainer-scrap --state open --limit 3 --json number,title,url,createdAt
If the result is empty, report that there are no open scrap issues and stop.
Step 2: Gather Each Issue's Content
For each scrap issue returned, read both the body and the discussion. Run these in parallel across the issues where practical:
gh issue view <issue_number>
gh issue view <issue_number> --comments
If an issue references related pull requests, commits, or files that are needed to understand it, gather that context as well.
Step 3: Understand and Summarize
For each scrap issue, explain the following based on its content:
- Topic: A one-line summary of what the scrap note is about.
- Background: The context, motivation, or problem the note captures and why it matters.
- Details / Findings: The specific observations, problems, or content recorded in the note.
- Proposed Solution / Next Steps: Any solution or actionable next step mentioned. If none is recorded, state explicitly that it is still undecided.
Keep each summary concise and focused. Present the issues in the order returned (newest first), with the issue number, title, and URL as a heading for each.
Use the language of the current conversation (follow the user's language).