bug-report

To generate a structured bug report, provide a plain description or code snippet context and the skill will output a standardized Markdown Bug Report with sections for Summary, Reproduction, Severity, Environment, and Evidence. It analyzes code paths to fill in missing fields and ensure complete reproduction steps.

The best way to add reproduction steps and severity assessment is to convert your bug scenario into a standardized Markdown bug report. This process identifies expected versus actual results, assesses severity, and structures the context for direct submission to issue trackers or CI pipelines.

Yes, you can analyze code paths to fill in missing bug report fields. The skill performs contextual augmentation by searching the codebase to surface relevant files and traces, which improves the accuracy of the reproduction steps and environment details in the final report.

Yes, this bug reporting approach works for software projects of any size and languages. It takes plain descriptions or code analyses and structures them into a standardized Markdown Bug Report, making it suitable for diverse codebases and CI pipeline integrations without requiring specific dependencies.

A standardized Markdown bug report for CI pipelines includes specific sections for Summary, Classification, Environment, Reproduction, and Evidence. This structure ensures that contextual details and severity assessments are consistently captured for faster triage and fixes.