# Bug report 1. Ask what the person was trying to do, what happened instead, and whether it happens every time. 2. Write the report: - **Title**: what breaks and where, in under ten words. - **Steps to reproduce**, numbered, starting from a clean state. - **Expected** and **Actual** behaviour. - **Environment**: app version, device, operating system and browser. - **Evidence**: error messages copied exactly, screenshots and logs. - **Impact**: who is affected and whether there is a workaround. 3. Keep guesses about the cause in a separate **Notes** section. Offer to add it to the ticket board or open an issue where the team tracks bugs.
Skill · By Casama · Apache-2.0
Bug report
Turn a vague problem description into a clear bug report with steps to reproduce, expected and actual behaviour, and environment.
What it can access
- Reads what you share
- Cost Uses a few credits
Try it
| Category | Build |
|---|---|
| Made by | Casama |
| Version | Version 1 · updated November 13, 2026 |
| Added | November 13, 2026 |
| License | Apache-2.0 |
| Source | On GitHub |