bug-report-writer
Skill2 starsChanged 8 months agoMITView on GitHub
4 other projects use a version of this.
Adopted by
Most recently taken up by
- godhiraj-code/greenbuild-plugintheir own version, first seen Nov 1, 2026
- 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
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
- ShreyasBh02/AI-Skills-Collection★ 2same name
- godhiraj-code/greenbuild-plugin★ 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 repository21 other files it gives its agents.
- appendix-assemblerSkill
- architecture-record-writerSkill
- decision-log-writerSkill
- design-rationale-writerSkill
- evaluation-report-writerSkill
- reference-integrity-checkerSkill
- spec-writerSkill
- test-case-table-builderSkill
- test-plan-writerSkill
- traceability-matrix-writerSkill
- appendix-assemblerSkill
- architecture-record-writerSkill
- bug-report-writerSkill
- decision-log-writerSkill
- design-rationale-writerSkill
- evaluation-report-writerSkill
- reference-integrity-checkerSkill
- spec-writerSkill
- test-case-table-builderSkill
- test-plan-writerSkill
- traceability-matrix-writerSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
6
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 12
Write precise, reproducible defect reports that improve triage and rework quality.
- Distinctive: line 49
Prefer structured, reusable artifacts over generic prose.
- Distinctive: line 55
Do not fabricate evidence, references, or approval.
- Distinctive: line 56
Do not collapse requirements, decisions, tests, and findings into one undifferentiated blob.
- Distinctive: line 57
Do not leave identifiers or document links inconsistent.
- Distinctive: line 58
Do not confuse “described” with “verified”.
“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
Purpose
Write precise, reproducible defect reports that improve triage and rework quality.
Trigger this skill when
- A durable documentation or evidence artifact is needed for review, submission, audit, or handover.
- You need clearer linkage between requirements, design, testing, defects, decisions, or findings.
- Existing documentation is fragmented, inconsistent, or weakly evidenced.
Expected inputs
- observed defect
- reproduction notes
- environment
- evidence
Deliverables
- bug report
- repro steps
- severity/priority suggestion
Operating procedure
- Clarify the artifact boundary, audience, and review objective.
- Separate known facts from assumptions, placeholders, and missing evidence.
- Produce the skill-specific artifact in a form that can be reused directly.
- Link the result to upstream and downstream artifacts where helpful.
- Recommend the next best handoff instead of trying to do every document at once.
Quality gates
- The output is specific to the current system, feature, or report context.
- Identifiers, references, and labels are internally consistent.
- Missing evidence or unresolved questions are made visible.
- The result is directly usable in a repo, report, appendix, or review packet.
Handoff targets
- test-case-table-builder
- evaluation-report-writer
- appendix-assembler
Output style
- Prefer structured, reusable artifacts over generic prose.
- Make IDs, labels, references, and evidence explicit where possible.
- Preserve traceability between related artifacts.
- Surface missing evidence or unresolved questions instead of inventing closure.
Failure modes to avoid
- Do not fabricate evidence, references, or approval.
- Do not collapse requirements, decisions, tests, and findings into one undifferentiated blob.
- Do not leave identifiers or document links inconsistent.
- Do not confuse “described” with “verified”.
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.

