bug-report

Records defects with reproduction, mechanism, and verified fixes in a JSON register.

Updated Aug 4, 2026
One-click install
npx skills add https://github.com/tschallacka/ai-skills --skill bug-report-tschallacka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/tschallacka/ai-skills/tree/main/bug-report
Command: npx skills add https://github.com/tschallacka/ai-skills --skill bug-report-tschallacka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Defects found mid-work often get lost, vaguely described, or closed without proof. This Skill maintains a single BUGS.json register where every entry carries its reproduction, observed versus expected behavior, root-cause mechanism, and the verification that fails without the fix. ## Core Features & Use Cases - Validated writes via the bugs binary: bugs add and bugs update enforce required fields and fixed vocabularies for status, severity, and priority, refusing malformed entries. - Evidence-backed closure: Marking an entry fixed requires both a fix reference and a verification naming the mutation that fails without it; dismissals require reasoning. - Register maintenance tooling: Commands for tree/report/list views, schema migration between versions, merge-conflict resolution, and duplicate-id deduplication. - Use Case: During a code review you find a heading-rename bug you cannot fix now. Run bugs add with the reproduction command and observed output, then later close it with the commit hash and the test that proves the fix. ## Quick Start Ask the agent to record the defect you just found as a new entry in BUGS.json using the bugs command with its reproduction steps and observed output.

Frequently Asked Questions about bug-report

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

FAQPage Schema
How do I record a bug with reproduction steps in a JSON register?▼

Run `bugs add` with --title, --reproduce, --observed, and --expected flags; all four are required and the command refuses without them. Long prose can be supplied via -file counterparts like --reproduce-file to avoid shell-quoting issues.

How do I close a bug entry with proof of the fix?▼

Run `bugs update <id> --status fixed` together with --fix naming the commit and --verification describing how the fix was proven, including the mutation that fails without it. The command refuses a fixed status without verification.

Does the bugs tool work on macOS and Windows?▼

Yes, the bugs binary ships per target triple under bin/<target-triple>/, covering Linux (x86_64, aarch64), macOS (Intel and Apple Silicon), and Windows (MSVC). It is a single prebuilt binary needing no shell or other tools.

What happens when BUGS.json was written by an older skill version?▼

The bugs binary refuses to read it and names the version found. Run `bugs migrate`, which backs up the file before parsing, converts entries that fit the current schema, and reports anything needing manual re-filing.

When should I not use a bug register?▼

Do not use it for queued work like refactors or migrations (use a todo register), for defects being fixed in the current change (write a test instead), or for design disagreements, which belong in a decision record.