bug-report-writer
Skill4 starsChanged 27 days agoMITView on GitHub
Use when writing or improving a bug report, defect ticket or Jira/GitHub issue from notes, screenshots, logs, a video description or a failed test, so developers can reproduce and fix it quickly.
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
- 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
- 45ck/documentation-evidence-skills★ 2same 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 repository30 other files it gives its agents.
- accessibility-auditSkill
- api-design-reviewSkill
- api-test-writerSkill
- architecture-diagramSkill
- bug-debuggerSkill
- changelog-writerSkill
- codebase-onboardingSkill
- code-reviewSkill
- database-schema-designSkill
- dependency-upgradeSkill
- design-handoff-specSkill
- design-reviewSkill
- dockerize-appSkill
- figma-design-compareSkill
- flaky-test-fixerSkill
- git-commit-writerSkill
- github-actions-ciSkill
- playwright-e2e-testsSkill
- prd-writerSkill
- proof-of-done-liteSkill
- readme-writerSkill
- refactor-plannerSkill
- security-auditSkill
- seo-auditSkill
- test-case-generatorSkill
- test-plan-writerSkill
- test-writerSkill
- ux-research-synthesisSkill
- ux-writingSkill
- web-performance-auditSkill
The file
Files
Bug Report Writer
Overview
A good bug report lets a developer reproduce the problem on the first try. State exactly what happened, what should have happened, and how to make it happen again, with only the evidence that matters.
Method
- Collect facts from what the user provides: steps, screenshots, console or server logs, failing test output, environment.
- Reduce the steps to the shortest path that triggers the bug. Remove steps that do not matter.
- Separate observation from guesses. Facts go in the report; suspected causes go in a clearly labelled Notes line.
- Find missing essentials (environment, build version, account type, data used). Ask for them, or mark them
Unknown. - Set severity and priority with the table below.
- Write using the format. Keep the title searchable.
Format
Title: <Area>: <what goes wrong> when <condition>
e.g. "Checkout: total ignores coupon when quantity is changed"
Environment: <app/build version, URL, browser/OS or device, account role, feature flags>
Severity: <Blocker | Critical | Major | Minor | Trivial> Priority: <P1-P4>
Steps to reproduce:
1. ...
2. ...
Expected result: <what should happen, with the rule or spec reference if known>
Actual result: <what happens, exact error text>
Reproducibility: <Always | Intermittent (3 of 10 tries) | Once>
Evidence: <screenshot or video name, log excerpt (only relevant lines), request/response, test name>
Test data: <account, IDs, input values>
Notes: <suspected cause, workaround, first build where seen> (optional)Severity guide
| Severity | Meaning |
| Blocker | Stops testing or a release; no workaround |
| Critical | Core flow broken, data loss, security or payment issue |
| Major | Feature works incorrectly; workaround exists |
| Minor | Cosmetic or rare edge case with little impact |
| Trivial | Typo or tiny visual issue |
Common mistakes
- Titles like "Bug in app" or "Not working".
- Steps that start in the middle ("go to the form" — which form, which user?).
- Pasting 500 lines of logs instead of the relevant 10.
- Mixing two bugs in one report.
- Presenting a guessed cause as fact.
Made by Wageesha Tripathi · LinkedIn · Email · More 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.