Reports to QA action

AI prompts: Bug triage

Prompts that turn vague bug reports, support tickets, logs, and PRs into evidence, severity, owners, and next tests.

Data security: Use these prompts with your coding agent or QA workflow. Avoid pasting secrets, credentials, or sensitive customer data into tools you do not control.

Turn a bug report into reproduction steps

Use this when a bug report is messy, vague, or incomplete.

You are a QA engineer.
Analyze this bug report and rewrite it into clear reproduction steps:
[PASTE BUG REPORT]

Return:
1. Clean bug title
2. Environment
3. Preconditions
4. Step-by-step reproduction steps
5. Actual result
6. Expected result
7. Severity
8. Priority
9. Missing information
10. Suggested automated regression test

Check if a bug is valid or expected behavior

Use this for issue triage.

You are a QA lead helping with bug triage.
Analyze the following issue:
[PASTE BUG REPORT]

Product context:
[PASTE PRODUCT CONTEXT OR REQUIREMENTS]

Decide whether this is likely:
- A valid bug
- Expected behavior
- Missing requirement
- UX issue
- Configuration issue
- Cannot reproduce

Explain your reasoning.

Then provide:
1. What evidence is needed
2. What should be tested next
3. Suggested severity
4. Suggested owner: frontend / backend / product / design / infrastructure

Analyze logs and suggest QA checks

Use this when production logs reveal recurring errors.

You are a QA engineer analyzing application logs.
Analyze these logs:
[PASTE LOGS]

Identify:
1. Possible user-facing issues
2. Root-cause hypotheses
3. Affected user flows
4. Test cases that should be added
5. Monitoring checks that should be created
6. Severity and priority

Return the answer as a QA action plan.

Find high-risk areas in a pull request

Use this with a diff, PR description, or changed files.

You are a QA lead reviewing a pull request.
Analyze this PR and identify what should be tested:

PR description:
[PASTE PR DESCRIPTION]

Changed files:
[PASTE FILE LIST OR DIFF SUMMARY]

Product context:
[DESCRIBE PRODUCT AREA]

Return:
1. High-risk areas
2. User flows that may be affected
3. Regression test checklist
4. Suggested automated tests
5. Suggested manual tests
6. Questions for the developer
7. Release risk: Low / Medium / High

Turn customer support tickets into QA tests

Use this when support tickets reveal repeated problems.

You are a QA engineer reviewing customer support tickets.
Analyze these support tickets:
[PASTE SUPPORT TICKETS]

Identify:
1. Repeated product issues
2. Bugs that should be reproduced
3. Missing regression tests
4. Monitoring checks that should be added
5. UX problems that may not be bugs
6. Suggested priority

Then create test cases based on the most important tickets.

Other areas

Requirements to QA coverage Test planning Human QA sessions Exploratory testing Changed flows and releases Regression testing Flows to automated QA Playwright test generation Endpoints and contracts API testing Things likely to break Edge cases Ship with confidence Release QA CI stability Flaky test debugging Always-on QA Monitoring checks