bug-reporting-excellence

Bug Reporting Excellence is a specialized quality engineering skill designed to eliminate ambiguity in defect tracking. It provides a structured communication framework that transforms vague bug reports into actionable engineering tasks. The skill is intended for QA engineers, software developers, and technical leads who need to minimize the back-and-forth cycle between reporting an issue and verifying a resolution. By enforcing a strict 'One Bug = One Report' policy and providing a standardized schema for environment details, steps to reproduce, and impact analysis, this skill ensures that development teams have all the diagnostic data required to prioritize and fix bugs efficiently.

• Standardized reporting schema incorporating components, severity levels, environment, expected vs. actual behavior, and clear reproduction steps.

• Built-in logic for isolating variables such as browser versions, OS details, request IDs, and specific user conditions to narrow down root causes.

• Integration patterns for automated bug triage and duplicate detection using established QE agents like qe-quality-analyzer and qe-production-intelligence.

• Anti-pattern detection to prevent common mistakes like conflating multiple bugs or providing insufficient reproduction context.

• Severity assessment guidelines ranging from critical system-down events to cosmetic UI edge cases.

• Utilize this skill when performing manual testing, mentoring junior team members on quality documentation, or integrating bug reporting into CI/CD workflows.

• Inputs typically include raw observation data, logs, console output, and screenshots, which the agent synthesizes into a professional report.

• Outputs are formatted as markdown reports suitable for Jira, GitHub Issues, or internal project management trackers.

• Adhere to the provided checklists, such as the Critical Success Factors (e.g., 100% reproducible steps, 80% evidence inclusion), to maintain a high trust tier for all reports generated.

• Connect this skill with technical-writing and root-cause-investigation workflows to build a comprehensive feedback loop that improves overall product quality and developer velocity.