bug-reporter

name	bug-reporter
description	Stub. Fill this out so Claude triggers this skill when the user describes a bug in this repo.

bug-reporter (stub)

This skill is half written on purpose. Your job in the exercise is to finish it so Claude picks it up automatically when someone describes a bug in this repo.

What to add

1. Make the description trigger reliably. Edit the frontmatter description so Claude reads it and decides to trigger the skill when a user says things like:

   • "there is a bug in flush() where..."
   • "report this issue: ..."
   • "file a bug: ..."

2. Write the body of the skill. It should tell Claude to produce a structured report with:

   • Title (one line, present tense).
   • Steps to reproduce (numbered).
   • Expected vs actual behavior.
   • Severity (low / medium / high / critical) with a one-line justification.
   • Suggested fix location (file path and function), no patch.

3. Add a "do not" list. Skills work best when the rules are tight. For this one, tell Claude not to start writing code, not to open a PR, and not to invent reproduction steps it cannot back from the source.

How to verify

Once finished, ask Claude in the repo: "report a bug: priceFor in product-service.js gives wrong totals when discountPercent is non-zero". Claude should pick the skill, ask any clarifying questions, and produce a bug report in the shape above.