What problem does it solve? Writing a bug report that developers can act on without follow-up questions is hard: missing environment details, vague actual results, and inconsistent severity ratings slow down triage and fixes. This Skill turns raw evidence (screenshots, logs, test output) into a complete, standardized defect ticket. ## Core Features & Use Cases - Evidence-first extraction: Pulls failure details from screenshots, recordings, console logs, and failing assertions before asking the user anything, then collects all missing fields in a single message. - Structured ticket template: Produces a full Jira-ready report with summary, environment, device/browser, numbered reproduction steps, expected vs actual results, attachments, severity, priority, and traceability fields (Finding ID, journey, build/commit, reproduction test). - Severity and priority guidance: Suggests severity from concrete rules (crash/data loss → Critical, cosmetic → Low) and pre-fills priority from the bug-discovery severity × journey-tier matrix, always requiring user confirmation. - Use Case: After an automated test run flags a failing login flow, hand the assertion output and screenshot to the agent and receive a pre-filled, confirmation-gated bug ticket with verbatim error messages and credential-store references instead of plaintext secrets. ## Quick Start Ask the agent to file a bug report for the failing checkout flow using the attached screenshot and console log.
