list-bugs
Skill0 starsChanged 5 months agoMITView on GitHub
List and summarize bugs from docs/bugs.md, with optional filtering by status, severity, or area.
In this repository4 other files it gives its agents.
- add-bugSkill
- add-featureSkill
- fix-bugSkill
- review-my-codeSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Distinctive: line 30
If filtered: "3 of 8 bugs match filter"
- Very specific: line 41
If docs/bugs.md has no bug entries, say "No bugs tracked yet.
- Distinctive: line 42
If filters match nothing, say "No bugs match that filter" and show the total count of all bugs.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
List Bugs
Display a summary of bugs tracked in docs/bugs.md.
Process
- Read
docs/bugs.md— Parse all bug entries. Apply filters — If the user provided arguments, filter by:
- Status:
reported,confirmed,in-progress,fixed,wont-fix - Severity:
critical,high,medium,low - Area:
<area-1>,<area-2>,<area-3>(your project's configured areas)
Arguments are matched case-insensitively. Multiple filters narrow the results (AND logic). If no arguments are given, show all open bugs (everything except Fixed and Won't Fix).
- Status:
- Display as a table — Output a markdown table with these columns:
| ID | Status | Severity | Area | Title | Reported |- Show a count summary — Below the table, show totals like:
- "5 bugs shown (2 Critical, 1 High, 2 Medium)"
- If filtered: "3 of 8 bugs match filter"
Examples
/list-bugs— All open bugs/list-bugs critical— Only critical severity/list-bugs reported <area-1>— Reported bugs in a specific area/list-bugs all— Everything including Fixed and Won't Fix
Edge cases
- If
docs/bugs.mdhas no bug entries, say "No bugs tracked yet. Use/add-bugto log one." - If filters match nothing, say "No bugs match that filter" and show the total count of all bugs.
Configuration
Replace these placeholders with your project's values before using the skill:
<area-1>,<area-2>,<area-3>— the modules / sub-projects in your repo used to filter bugs by area (e.g.frontend,backend,api). Keep this list identical to the areas defined inadd-bug.
See the repository README for the full placeholder reference shared across skills.
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.

