Coding & Debugging Prompts

Bug Reproduction Report Writer

Turn a description of a bug into a clear, structured reproduction report that developers can act on quickly.

✱ By PiSkill TeamFreeClaudeChatGPTGeminiMicrosoft Copilot

Best for

QA testers, developers, and product managers who need to turn a rough bug description into a clear, actionable report for a development team.

Suitable LLM groups

FrontierReasoning

Prompt

You are acting as a QA engineer who helps me write a clear, useful bug reproduction report. You must not invent logs, stack traces, version numbers, or test results that I have not provided. If key details are missing, list them as information still needed rather than guessing.

Here is my information:

What happened: {{input_text}}
What I expected to happen: {{desired_output}}
Environment details I know, such as browser, device, or app version: {{context}}
Steps I took before the bug occurred: {{examples}}
How often this happens: {{constraints}}
Any error messages I saw, if any: {{goal}}

If important details needed for a developer to reproduce this bug are missing, ask me clarifying questions before writing the report.

Please produce a structured bug report with the following sections:

1. Bug summary: A short, clear one to two sentence summary of the issue.
2. Environment: List the environment details provided, such as device, browser, operating system, or app version.
3. Steps to reproduce: List the exact steps taken before and during the bug, numbered in order.
4. Expected behavior: Describe what should have happened.
5. Actual behavior: Describe what actually happened instead.
6. Screenshots or logs needed: List what screenshots, logs, or additional evidence would help a developer investigate, without inventing any yourself.
7. Severity: Suggest a severity level, such as low, medium, high, or critical, based on the impact described.
8. Developer notes: Add any additional observations that might help a developer investigate, clearly separating fact from speculation.

Do not invent error messages, stack traces, version numbers, or logs that were not provided. If such details would help but are missing, list them under information still needed.

How to use

Describe what happened, what you expected, and any environment details you know.
List the exact steps you took before the bug occurred.
Run the prompt in your preferred AI tool.
Answer clarifying questions if key reproduction details are missing.
Submit the structured report to your development or QA tracking tool.

Example input

What happened: the app crashes when I try to upload a profile photo larger than 5MB. Expected: the app should either resize the photo or show an error message. Environment: iPhone 13, iOS 17, app version 2.4.1. Steps: opened profile settings, tapped upload photo, selected a large photo from camera roll. Frequency: happens every time with large files.

Example output

Bug summary: the app crashes when a user attempts to upload a profile photo larger than 5MB, instead of resizing it or showing an error.
Environment: iPhone 13, iOS 17, app version 2.4.1.
Steps to reproduce: open profile settings, tap upload photo, select a photo larger than 5MB from the camera roll, observe the app crash.
Expected behavior: the app should resize the photo automatically or display a clear error message about the file size limit.
Actual behavior: the app crashes immediately after selecting the oversized photo, with no error message shown.
Screenshots or logs needed: a screen recording of the crash, the exact file size and format of the photo used, and device crash logs if available.
Severity: high, since this is a full app crash that occurs consistently and affects a core profile feature.
Developer notes: the issue appears consistently with large files based on the reporter's testing, though the exact file size threshold that triggers the crash has not been confirmed and is listed as information still needed.

Customization tips

— Add screen recordings or exact error text if you have them for a more complete report.
— Request the report reformatted to match your team's specific bug tracker template.
— Ask for the severity assessment to be reconsidered if you have more context about business impact.
— Combine multiple related bug reports if they appear to share a root cause.

FAQ

No, it will never fabricate logs, stack traces, or version numbers, and will list missing details as information still needed.

Rate this prompt

How helpful was this?

Comments

Sam O.

Used this to ship 6 SEO articles in a week — the FAQ block alone is worth it.

Ines P.

Wish it had a Spanish voice preset, but overall very solid.

Related Skills

Code ImprovementFree

Code Review Assistant Skill

A practical AI code reviewer that finds bugs, security risks, and readability issues — and explains why each one matters.

ClaudeClaude CodeCowork

#code review#bug detection#security

✱ By PiSkill Team● Safe & Reviewed

View Details

Related articles coming soon — visit the Learn hub.