bug-report-writer
Skill1 starsChanged 28 days agoMITView on GitHub
Turn rough notes, screenshots, or logs into a clear, reproducible bug report formatted for the user's tracker.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- WST2002/claude-code-skillstheir own version, first seen Oct 17, 2026
- Marina-Gajego/qa-skillstheir own version, first seen Oct 11, 2026
- ShreyasBh02/AI-Skills-Collectiontheir own version, first seen Mar 30, 2026
- 45ck/documentation-evidence-skillstheir own version, first seen Mar 28, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- Marina-Gajego/qa-skills★ 5same name
- WST2002/claude-code-skills★ 4same name
- 45ck/documentation-evidence-skills★ 2same name
- ShreyasBh02/AI-Skills-Collection★ 2same 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 repository16 other files it gives its agents.
- accessibility-auditSkill
- api-test-generatorSkill
- automation-code-reviewSkill
- ci-cd-and-test-dataSkill
- device-cloud-setupSkill
- flaky-test-triageSkill
- framework-scaffolderSkill
- greenbuild-getting-startedSkill
- llm-app-testingSkill
- mobile-automationSkill
- performance-test-starterSkill
- regression-health-digestSkill
- release-readiness-checklistSkill
- test-plan-from-requirementsSkill
- tools-and-librariesSkill
- visual-testingSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 6
Read the raw input. Ask only for what is missing and blocking: steps, expected vs actual, environment.
- Distinctive: line 13
Frequency: always or x/y attempts
- Distinctive: line 17
Remove secrets, tokens and personal data from logs.
“Common” is measured: kept by at least 6 in 10 of the 3 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.
Files
Bug report writer
- Read the raw input. Ask only for what is missing and blocking: steps, expected vs actual, environment.
- Write:
- Title: [Area] Symptom when Action (under 80 characters, no "doesn't work")
- Environment: build/version, browser/device, OS, env (staging/prod), account type
- Preconditions
- Steps to reproduce: numbered, one action per step
- Expected / Actual
- Frequency: always or x/y attempts
- Evidence: screenshots, video, console/network errors, request IDs
- Severity (impact) and Priority (urgency), each with a one-line justification, kept separate
- Notes: workaround, regression since version X, suspected area
- Remove secrets, tokens and personal data from logs.
- Format for the tracker saved in memory (Jira fields or GitHub markdown).
- Show a draft. Never file it without explicit approval.
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.