Write a bug report

What it asks you for

What went wrongrequired

What you saw, in your words.

Where

Browser, version, account, anything relevant.

What it tells the AI to do

Turn this into a report a developer can act on.

Symptom: {{ symptom }}
Context: {{ context | default("not given") }}

A bug report is a reproduction, not a complaint. Produce:

1. **Title**: the behaviour, specific enough to search for later.
2. **Steps**: numbered, starting from a state anyone can reach. Not "go to the
   page" but which page, signed in as what.
3. **Expected** and **actual**, as separate lines. The gap between them is the
   bug; a report that only states one leaves the reader guessing which.
4. **Scope**: does it always happen, or only sometimes? Only on one account?
   Only after some other action?

Where you do not know something, write "unknown" rather than a plausible guess.
A wrong repro step costs more than a missing one, because it sends someone
looking in the wrong place.

Then file it as a task.

Why this works

A bug report is a reproduction, not a complaint, and the gap between the two is why tickets sit untouched. This asks for the state a developer starts from, separates expected from actual, and marks what you do not know as unknown rather than filling it with a plausible guess: a wrong repro step costs more than a missing one because it sends someone looking in the wrong place.

Questions

What if I cannot reproduce it reliably?

Say so. Intermittent is a real and useful finding, and the scope section captures how often and under what conditions. Reporting it as reliable when it is not wastes the first hour of the investigation.

• bug
• report
• repro
• issue

More code skills

• idapt CodeWork on a real codebase through a paired or cloud computer, including implementation, tests, git, and delivery.
• Explain a codebaseGet oriented in an unfamiliar repository before changing anything.
• Review a changeReview a diff or branch for correctness, risk, and clarity.
• Write testsAdd tests that would actually have caught the bug.
• Build a web appBuild a small web app and deploy it to its own idapt subdomain.
• Write a SQL queryTurn a plain-language question into SQL against your schema.