bug-report
/bug-report
Write a clear, reproducible bug report from rough notes, logs, screenshots descriptions or a conversation: title that states the failure, minimal steps, expected vs actual, environment, evidence, impact, and separate severity and priority suggestions; formatted for Azure DevOps or Jira. Use whenever a defect must be logged or an existing report is too vague to act on.
- Author
- RobinBeraud ↗
- Repository
- claude-qa-skills ↗
- Licence
- MIT
- Last repository change
- 10.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Write a clear, reproducible bug report from rough notes, logs, screenshots descriptions or a conversation: title that states the failure, minimal steps, expected vs actual, environment, evidence, impact, and separate severity and priority suggestions; formatted for Azure DevOps or Jira. Use whenever a defect must be logged or an existing report is too vague to act on.
Original author description
Write a clear, reproducible bug report from rough notes, logs, screenshots descriptions or a conversation: title that states the failure, minimal steps, expected vs actual, environment, evidence, impact, and separate severity and priority suggestions; formatted for Azure DevOps or Jira. Use whenever a defect must be logged or an existing report is too vague to act on.
How it works
- Steps
- Output
- Never
SKILL.md preview
--- name: bug-report description: "Write a clear, reproducible bug report from rough notes, logs, screenshots descriptions or a conversation: title that states the failure, minimal steps, expected vs actual, environment, evidence, impact, and separate severity and priority suggestions; formatted for Azure DevOps or Jira. Use whenever a defect must be logged or an existing report is too vague to act on." --- # Bug report Cem Kaner's **RIMGEA**: Replicate, Isolate, Maximize (show the worst consequence), Generalize (find the broader case), Externalize (impact on users), And say it dispassionately. ## Steps 1. **Title**: `<where> - <what fails> when <condition>`. e.g. "Invoice export - VAT total off by 0.01 EUR when lines have 3 decimals". 2. **Steps**: numbered, minimal, starting from a known state, with exact data. 3. **Expected** vs **Actual**, each one sentence, with values. 4. **Environment**: version/build, environment, browser/OS, tenant, user role, feature flags. 5. **Evidence**: log excerpt (trimmed, no secrets), screenshot names, request id / correlation id, timestamp with time zone. 6. **Scope**: what else is affected (generalize), what is *not* affected (isolate). 7. **Impact**: who is hurt, how often, workaround. 8. **Severity** (technical impact) and **priority** (business urgency) as *suggestions*, kept separate. ## Output Markdown ready to paste, with an Azure DevOps field mapping when relevant (Repro Steps, System Info, Severity, Priority, Area Path, Tags). ## Never Blame people, include personal data or credentials, or mix two bugs in one report.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · RobinBeraud/claude-qa-skills | 90 | MIT |
| diegopacheco/ai-playground | 100 | Unlicense |
| CharlieJamesGwapo/claude-work-skills | 100 | MIT |
| MohamedRamadanSalah/claude-qa-toolkit | 100 | MIT |
| pipecat-ai/gradient-bang | 100 | Apache-2.0 |
| chatquill/claude-code-websites | 85 | MIT |
Database snapshot: 13.11.2026 · package version a41fd39ff0a9 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100report-bug
Creates structured bug report documents with reproduction steps, expected vs actual behavior, and severity classification. Use when the user asks to "report a bug", "file a bug", "document a defect", "log an issue", or mentions a bug, defect, regression, or unexpected behavior… - 100create-bug
Use when an agent or user needs to file a bug, report an issue, create a defect ticket, or capture a sub-agent blocker. Creates well-formatted, evidence-based bug tickets by collecting reproduction steps, expected vs. actual behavior, environment details, and logs, then writing… - 82analyze
Analyze a ticket, issue or bug report (Azure DevOps, GitHub, Jira or pasted text) by cross-checking docs/wiki, code, git history and data to find where the problem is and propose the minimal fix. Works in any repo. Use when the user asks to analyze/read a ticket, issue, PBI,… - 90qa-bug-report
Write a bug report a developer can reproduce on the first try — environment and build, account role, preconditions, numbered steps, expected result with its source versus actual, evidence (screenshot, console, request, response, requestId), reproducibility, severity and priority… - 100bug-report-template
Builds a well-formed bug (defect) report from raw observation notes - fills in summary, environment, steps to reproduce, expected vs actual, and severity rationale - and validates that each field has the load-bearing content reviewers and engineers need to triage. Also converts… - 100jira-bug-ticket
Create a Jira bug ticket. Use when the user asks to file, log, report, or create a bug or defect in Jira ("create a bug ticket", "log a bug", "report a bug", "open a ticket for this bug").