Bug Report Your Agent Can Fix (free sample)
by PaperChaseWebb
From the $14 pack: the capture checklist, the report template, five rules and the reproduce-first prompt.
- Price
- Free
- Difficulty
- Beginner
- Setup
- 5 min
- Format
- .md file
bug-report-your-agent-can-fix-free-sample.md · 2 KB · direct download, no signup
What you end up with
Your next bug report has what a coding agent needs to reproduce it.
What you get
- The capture checklist
- The report template
- Five rules
- The reproduce-first prompt
Who it is for
Anyone who wants a better bug report today.
Works with
Solid chips: the agent is named in this listing's own tools list. Dashed chip: Plain Markdown, so it also pastes into other agents such as Grok Bot, Hermes, OpenClaw or Muse. We list those as compatible by format only, not as tested.
Tools needed
Cost to run: Free.
Time to result: About five minutes
Sample prompts, free to use
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.
The rest is in the file.
Free preview of the file
# 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
Test record
- Date
- Oct 30, 2026
- What was run
- The template in the sample checked with bug_check.py.
- Result
- Only B15 (unticked box) on the blank template, as expected.
- Not run
- Agent runs.
Copied from this item's dated test notes. What was not run stays in.
Worth knowing
- The redaction script, the checker, the other three prompts, the worked example and the tests are in the full pack.
- Tested 2026-10-30: the blank template run through bug_check.py flags only B15, as expected.
Questions
What is in the full pack?
redact.py, a 16-check bug_check.py, four prompts that reproduce, fix, test and write back, a worked example and 13 tests. $14.
Details
Version 1.0 · Updated Oct 30, 2026 · Markdown version of this page
License: Personal and commercial use. Download terms