---
name: qa-bug-report
description: Create clear bug reports from reproduction notes, screenshots, logs, test failures, or Jira issue context.
---

# QA Bug Report Skill

Use this skill when the user asks Copilot to write, improve, classify, or prepare a bug report for Jira.

## Inputs To Ask For

- Feature or module
- Environment, build, browser, device, and user role
- Reproduction steps
- Actual result
- Expected result
- Screenshots, logs, console errors, API responses, or test failure output
- Severity, priority, and affected release, if known

## Output Format

Create the bug report with these sections:

1. Title
2. Summary
3. Environment
4. Preconditions
5. Steps To Reproduce
6. Actual Result
7. Expected Result
8. Evidence
9. Impact
10. Severity And Priority
11. Workaround
12. Suspected Area
13. Regression Notes
14. Jira Fields To Populate

## Rules

- Keep the title short, specific, and searchable.
- Do not invent evidence. Clearly label missing evidence.
- Convert rough tester notes into reproducible steps.
- Explain severity and priority separately.
- If Jira MCP tools are available, check for duplicates, linked stories, components, labels, and release fields before drafting.
- If the user asks to create the Jira issue, summarize the fields first and ask for confirmation before submitting.

## Example Prompt

Create a Jira-ready bug report from these notes and check for possible duplicates in Jira before drafting: the checkout page accepts an expired card and shows success.