bug-reporting-excellence

The bug-reporting-excellence skill is a specialized quality engineering framework designed to eliminate ambiguity in defect communication. It provides a standardized formula for engineers, QA analysts, and product managers to document software issues, ensuring developers have all the necessary context for rapid resolution. By enforcing a rigorous structure—including component identification, precise environment details, expected versus actual behavior, and actionable reproduction steps—this skill minimizes the back-and-forth between reporting and development teams. It serves as an essential tool for establishing organizational quality standards and can be integrated directly into your CI/CD feedback loop or issue tracking systems like Jira, GitHub Issues, or Linear.

• Standardized Bug Formula: Enforces a consistent template (Component, Severity, Environment, Expected/Actual Behavior, Steps to Reproduce) to guarantee 100% reproducibility and clarity.

• Intelligent Triage & Coordination: Facilitates automated bug triage via the qe-quality-analyzer agent, duplicate detection, and root-cause analysis through the qe-production-intelligence agent.

• Severity Classification: Includes a comprehensive reference card for categorizing bugs from Critical (system down, data loss) to Low (cosmetic issues), ensuring prioritization alignment.

• Anti-Pattern Elimination: Explicitly avoids poor reporting habits like vague descriptions or bundling multiple distinct bugs into a single report, forcing modular, atomic issue tracking.

• Fleet Integration: Coordinates with the broader agentic-qe ecosystem, including technical-writing, exploratory-testing-advanced, and sherlock-review, to streamline the entire quality engineering lifecycle.

• Always provide precise environment details such as browser versions (Chrome, Firefox, Safari), OS, specific URLs, and unique request IDs to enable faster debugging.

• Use the provided Title Formula (Component fails Condition causing Impact) to ensure searchability and instant recognition in your project management dashboard.

• Attach concrete evidence such as JSON error logs, stack traces, console output, and screenshots, as these are critical success factors for developer intervention.

• When reporting production issues, reference deployment versions or specific PRs if known to assist in identifying potential regressions.

• Designed for high-velocity teams, this skill encourages the practice of one-bug-per-report, preventing ticket bloat and ensuring accurate progress tracking for engineering leads.