bug-report

To create a structured bug report from a natural language description, the skill automates generation of complete Markdown files with unique bug IDs, reproduction steps, and severity classification. It writes these reports directly to production/qa/bugs directories for immediate triage.

Tracking bug status and history is achieved through a disciplined lifecycle workflow that manages unique bug IDs, change logs, and verification steps. This ensures teams stay aligned by recording status updates and historical changes directly within the Markdown report files.

Yes, you can verify bug fixes and close resolved issues using the analyze, verify, and close workflows. The skill supports multi-mode analysis to validate fixes, update status, and record verification steps within the structured Markdown documentation.

This bug reporting workflow supports severity classification and root-cause analysis by generating reports that include environment details and root-cause hypotheses. It structures this contextual information to enable faster triage and resolution.

Bug reports are generated as structured Markdown files and stored in the production/qa/bugs directory. This format ensures compatibility with version control systems and easy integration into existing software engineering documentation workflows.

You need a standardized bug report format when triaging software issues that require consistent reproduction steps, severity assessment, and change history. This approach eliminates ambiguous reporting and accelerates the resolution process across development teams.