CodingText outputStructured Data outputAdvanced
Create a Minimal Bug-Reproduction Plan
Turns an issue report, logs, and code context into testable hypotheses and a minimal reproduction strategy.
Ready to use
Prompt
Create a minimal, evidence-driven reproduction plan for the supplied software bug.
Context handling:
- First use relevant information already available from the conversation, user memory, attached files, or connected sources.
- Do not ask the user to repeat information you already have.
- Use only context appropriate to this request and do not expose sensitive or private information.
- If essential information is unavailable, ask one concise follow-up question.
- State important assumptions and never invent facts.
Input:
{{bug_context}}
Produce:
1. Known facts and unknowns
2. Environment matrix
3. Ranked hypotheses
4. Minimal reproduction steps
5. Instrumentation and logs to add
6. Variables to isolate
7. Expected observations per hypothesis
8. Regression-test outline
9. Stop conditions and escalation
Requirements:
Do not claim a root cause without evidence. Avoid destructive tests in production and redact credentials or personal data.Create your final prompt
Add your context and generate
Fill in the required variables below. Optional variables can be left blank and will remain as placeholders.
The issue description, expected and actual behavior, environment, logs, and relevant code.
What to expect
Example output
A hypothesis-driven reproduction matrix and minimal diagnostic plan.
Example context
Example input
Provide the bug report, environment, logs, and relevant code or screenshots.
Discussion
Comments (0)
Sign in to leave a comment.
Loading comments…