summarizing-bugs
Skill131 starsChanged 8 days agoApache-2.0View on GitHub
Produces a quick status scan of open bug issues, optionally narrowed to one component and/or S2. Use when asked for a bug summary or the state of open bugs.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adding-chart-marksSkill
- adding-child-componentsSkill
- adding-propsSkill
- chart-featuresSkill
- comparing-time-periodsSkill
- filing-issuesSkill
- fixing-bugsSkill
- implementing-milestonesSkill
- s2-design-tokensSkill
- writing-rfcsSkill
- writing-s2-docs-pagesSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use when asked for a quick status scan of open bugs.
- Distinctive: line 38
Keep it a scan. If nothing matches, say so.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Bug Issue Summary
Use when asked for a quick status scan of open bugs. If the request names a component
(e.g. "line bugs") and/or s2, narrow to it.
Step 1 — List open bugs
gh issue list --repo adobe/react-spectrum-charts --state open --label bug --limit 200 \
--json number,title,labels,updatedAtTo narrow by component, add --label rsc:<Component> (e.g. rsc:Line; match the
capitalization of the existing labels). Add --label s2 for S2 only.
Sort by issue number ascending so a follow-up like "issue 3" can be resolved by re-running the same command.
Step 2 — Read bodies only if needed
Titles and labels are enough for most summaries. Run gh issue view <number> only when the
title leaves the bug's state genuinely unclear.
Step 3 — Report
Group by component label (issues with none go under "Other"). One line per issue:
**#<number>** <title> (<s2 if labeled>) — one clause on the symptom and, if known, how
settled the root cause is.Keep it a scan. If nothing matches, say so. End with a one-line total, e.g. "7 open bugs across Line, Donut, and Legend."
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.