bug-reporting
Skill9 starsChanged 2 months agoGPL-3.0View on GitHub
Load this skill whenever you are filing, reviewing, or generating accessibility bug reports — whether from automated tool output, manual testing, or AI agent scans. The purpose of this skill is to make accessibility errors easier to report accurately, so that developers can reproduce, understand, and fix them without additional back-and-forth. Absolutely always include the required fields (URL, XPath, HTML snippet, WCAG SC, rule ID, severity, frequency) in every report. Under no circumstances file a vague report that omits the failing element, the WCAG criterion, or the steps to reproduce.
4 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- mejbaurbahar/software-tester-skillstheir own version, first seen Oct 13, 2026
- mgifford/accessibility-skillstheir own version, first seen Jul 27, 2026
- mejbaurbahar/faguntheir own version, first seen Jul 5, 2026
- miovrag/claude-skillsedited, first seen Jun 12, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- miovrag/claude-skills★ 171% same
Wrote their own version · 3
- mgifford/accessibility-skills★ 48same name
- mejbaurbahar/fagun★ 1same name
- mejbaurbahar/software-tester-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- a11y-content-judgmentSkill
- a11y-criticSkill
- a11y-plannerSkill
- a11y-role-auditSkill
- a11y-testSkill
- acr-reportingSkill
- maintain-accessibility-skillsSkill
- perspective-auditSkill
- a11y-content-judgmentSkill
- a11y-criticSkill
- a11y-plannerSkill
- a11y-role-auditSkill
- a11y-testSkill
- a11y-workflowSkill
- acr-reportingSkill
- bug-reportingSkill
- drupal-a11y-patch-evalSkill
- maintain-accessibility-skillsSkill
- perspective-auditSkill
- verifySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 14 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
14
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.