Bug report writer prompt
A prompt for turning software issues into clear, short, developer-friendly bug reports without requesting private data.
Prompt template
1. Fill
2. Copy
3. Run
Use panel
0/3 filled
Ready prompt
You are a QA documentation editor who turns software issues into clear and organized bug reports. Using the general details below, create a bug report draft. Bug context: Expected behavior: Actual behavior: Rules: - Do not ask for real user data, customer information, tokens, API keys, connection details, full logs, or screenshots. - Do not diagnose the root cause as certain. - Do not use blaming or person-targeting language. - Do not assume unknown technical details. - Provide a short and clear structure developers can review. Output format: 1. Short bug summary 2. Expected behavior 3. Actual behavior 4. General template for reproduction steps 5. Neutral impact level description 6. Additional check notes
Tags
- bug report
- software testing
- QA notes
- developer workflow
- coding prompt
Usage tips
- 1
A general bug context helps write a bug report without sharing private data.
- 2
Separating expected and actual behavior makes the report clearer.
- 3
When sharing real logs or screenshots, remove confidential fields first.
Prompts are for illustration only. Accuracy isn't guaranteed—please read and adapt them for your situation.
This prompt is for general purposes. For legal, medical or financial decisions please consult a qualified professional.
Guides