# Bug Report Your Agent Can Fix (free sample)

From the $14 pack: the capture checklist, the report template and five rules. The full pack adds redact.py, a sixteen-check read-only bug_check.py, four prompts that reproduce, fix, test and write back, a worked example and 13 tests.

## The capture checklist (for whoever finds the bug)

1. Write down the time, with time zone.
2. Take a screenshot of the broken state.
3. Copy the console or log lines around the first error.
4. Note the failing request: method, path, status. Not the headers; they hold cookies.
5. Write the steps from a fresh start, one action per line, until it happens twice.
6. Note the app version or commit, browser and OS versions, and the kind of account.
7. Say what you expected to see.

## The report template

~~~markdown
# Bug report

## Summary
One sentence: what broke, where, for whom.

## Steps to reproduce
1. Start from: (page, screen or command)
2. Do: (each click, input or command, one per line)
3. See: (the moment it goes wrong)

## Expected
What should have happened.

## Actual
What happened instead, word for word if there is an error message.

## Environment
App version or commit, browser or OS and version, account type (no real names), device.

## Evidence
Screenshot or recording file names, the console lines around the error, the failing network request (method, path, status), the time it happened with time zone.

## Redaction
- [ ] redacted: ran redact.py on every log and checked screenshots for names, emails, tokens and card numbers

## Done when
The test or check that proves it is fixed, for example "steps 1 to 3 end on the receipt page and the new test passes".
~~~

## Five rules

1. Steps from a fresh start, numbered, one action each.
2. Exact error text, pasted.
3. One bug per report.
4. A "Done when" line the agent can test against.
5. Nothing private: mask emails, tokens and cookies before you share a log, and use test accounts in screenshots.

## One prompt to start

~~~text
Read report.md. Do not change any code yet. Reproduce the bug by following the steps exactly, or write a failing test that shows it, and show me the output. If you can not reproduce it, say which step differs and stop.
~~~