bug-report

Generates structured bug reports with reproduction steps, severity, and codebase context.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/onemanking/the-operator --skill bug-report-onemanking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/onemanking/the-operator/tree/main/.github/skills/bug-report
Command: npx skills add https://github.com/onemanking/the-operator --skill bug-report-onemanking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, actionable bug reports is time-consuming, and vague reports slow down triage and fixes. This Skill turns a short description or a code file into a complete, standardized bug report. ## Core Features & Use Cases - Structured Report Generation: Produces a full Markdown bug report with summary, severity, priority, classification, environment, reproduction steps, and evidence sections. - Codebase Context Search: Uses Grep and Glob to locate related files and list likely affected files and systems in the report. - Static Bug Analysis: The analyze mode reads target files and identifies potential bugs such as null references, off-by-one errors, race conditions, and unhandled edge cases, each with a likely trigger scenario and recommended fix. - Use Case: A QA tester observes a crash in the game and describes it in one sentence; the Skill searches the codebase and outputs a triage-ready report with severity, repro steps, and suspected root cause. ## Quick Start Ask the assistant to create a bug report describing the issue you observed, or run the analyze mode on a specific source file to detect potential bugs.

Frequently Asked Questions about bug-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a good bug report from a short description?

Provide a brief description of the issue and the Skill parses it, searches the codebase for related files, and generates a complete report with severity, priority, reproduction steps, expected versus actual results, and technical context.

How to find potential bugs in a source file automatically?

Invoke the analyze mode with a file path. The Skill reads the file and flags null references, off-by-one errors, race conditions, unhandled edge cases, resource leaks, and incorrect state transitions, each with a trigger scenario and recommended fix.

What sections does the generated bug report include?

The report includes summary with severity and priority, classification by category and frequency, environment details, reproduction steps with expected and actual results, technical context with likely affected files, evidence, and related issues.

Can the bug analysis detect race conditions and edge cases?

Yes, the analyze mode specifically looks for race conditions, unhandled edge cases, null references, off-by-one errors, resource leaks, and incorrect state transitions. Findings are heuristic and should be verified by a developer before filing.

What are the limitations of automated bug report generation?

The Skill cannot execute code or reproduce runtime behavior, so severity and root cause are inferred from the description and static code search. Reports still require human validation of reproduction steps and actual impact.