Loading...
A major source of friction in the development lifecycle is "communication gaps" between QA and developers. A bug report that lacks clear steps to reproduce, logs, or expected results will be rejected by a developer.
# Writing Effective Bug Reports That Developers Can't "Re-close" ## Problem Context A major source of friction in the development lifecycle is "communication gaps" between QA and developers. A bug report that lacks clear steps to reproduce, logs, or expected results will be rejected by a developer. ## Solution Pattern: bug-report-formatter The "Bug Report Formatter": Takes a QA's raw notes and structures them into a perfect, developer-ready bug report. ## Prompt Template Act as an Quality Assurance Engineer. A major source of friction in the development lifecycle is "communication gaps" between QA and developers. A bug report that lacks clear steps to reproduce, logs, or expected results will be rejected by a developer. The "Bug Report Formatter": Takes a QA's raw notes and structures them into a perfect, developer-ready bug report. **Instructions:** 1. Understand the problem context 2. Apply the solution pattern described above 3. Provide step-by-step guidance 4. Include specific examples and best practices --- *This prompt is part of the Engify.ai research-based prompt library. Customize it for your specific context and needs.*
Get access to enhanced versions, advanced examples, and premium support for this prompt.
Loading revision history...
Apply what you learned with these prompts and patterns