Coding
Bug Bash Consolidation and Fix Prioritization
Bug Bash Consolidation and Fix Prioritization turns technical context into clear code, diagnosis, or implementation guidance with clear constraints and an explicit output.
The prompt
Bug Bash Consolidation and Fix Prioritization guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning, writing, reviewing, or debugging software and you want a response that is easier to evaluate and act on.
text prompt
You are a QA lead.
Model guidance (Claude 4.6):
- Use extended thinking and set effort to high or max for complex synthesis.
- When given long context, cite specific excerpts by quoting short phrases and referencing their location (ex: section name) so humans can verify.
Task:
Consolidate the bug bash findings into a deduped list. Categorize, assign severity, identify owners, and propose a fix sequence with timelines.
Inputs:
- Bug bash findings list: {{bugList}}
- Release timeline: {{releaseTimeline}}
- Component ownership map: {{components}}
Output requirements:
- Use Markdown.
- Keep the top summary concise, then go deep.
- If key inputs are missing, list precise questions, then proceed with best-effort assumptions.
Output sections:
- Deduped issue list
- Severity and impact criteria
- Owner assignment
- Fix plan and sequencing
- Release gate recommendations
Tune the prompt, not the plumbing.
Every control comes from this prompt’s content schema. Changes stay in your browser and update instantly.
Customized prompt901 characters
You are a QA lead.
Model guidance (Claude 4.6):
- Use extended thinking and set effort to high or max for complex synthesis.
- When given long context, cite specific excerpts by quoting short phrases and referencing their location (ex: section name) so humans can verify.
Task:
Consolidate the bug bash findings into a deduped list. Categorize, assign severity, identify owners, and propose a fix sequence with timelines.
Inputs:
- Bug bash findings list: a specific bug list
- Release timeline: a specific release timeline
- Component ownership map: a specific components
Output requirements:
- Use Markdown.
- Keep the top summary concise, then go deep.
- If key inputs are missing, list precise questions, then proceed with best-effort assumptions.
Output sections:
- Deduped issue list
- Severity and impact criteria
- Owner assignment
- Fix plan and sequencing
- Release gate recommendations
Useful structure, room to move.
Bug Bash Consolidation and Fix Prioritization guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning, writing, reviewing, or debugging software and you want a response that is easier to evaluate and act on.
The prompt establishes the job first, then supplies concrete decisions a model can act on. The variables preserve that structure while letting you change the subject, context, or output.
Related prompts
Bug Report Triage and Repro Steps
Bug Report Triage and Repro Steps turns technical context into clear code, diagnosis, or implementation guidance with clear constraints and an explicit output.
ChatGPTClaudeGemini
Error Message Explainer
Error Message Explainer turns technical context into clear code, diagnosis, or implementation guidance with clear constraints and an explicit output.
ChatGPTClaudeGemini
Security Checklist for New Feature
Security Checklist for New Feature turns technical context into clear code, diagnosis, or implementation guidance with clear constraints and an explicit output.
ChatGPTClaudeGemini
Agentic Memory Code Reviewer
Agentic Memory Code Reviewer turns technical context into clear code, diagnosis, or implementation guidance with clear constraints and an explicit output.
ChatGPTClaudeGemini