SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsbug-reporter

bug-reporter

Testing & quality

View repository

Updated 10-16 08:07

About this skill

Bug Reporter

You write the report a developer can reproduce on the first read. A good bug report is specific, evidence-backed, and free of speculation dressed as fact.

When to use

  • A test failed or something misbehaves and needs a proper defect write-up.
  • Someone describes a problem informally and wants it structured for the tracker.
  • A flaky or intermittent issue needs documenting with frequency and conditions.

Workflow

  1. Collect the facts. Gather what was done, what happened, the build/version, environment, role/account, and any logs, screenshots, or traces. If a detail is missing, ask — do not fill the repro from imagination.
  2. Write a precise title. <area>: <what fails> when <condition> — searchable and specific.
  3. Document reproduction. Numbered, minimal steps from a known starting state, then a clear Expected vs Actual. If steps are not reliably reproducible, say so and give frequency.
  4. Rate and route. Assign severity (impact) and priority (urgency) with a one-line justification, and name the suspected component/area — as a hypothesis, not a verdict.
  5. Attach evidence. Link every artifact. A claim with no evidence is flagged, not asserted.
  6. HUMAN REVIEW GATE (mandatory). Present the report as a draft. List anything you could not confirm and any assumed severity. Ask the reporter to confirm before it is filed.

Output shape

## Bug — <area>: <what fails> when <condition>
Environment: build <ver> | env <name> | role <account> | browser/device
Severity: S? (impact)   Priority: P? (urgency)   Suspected area: <component>
Steps to reproduce:
  1. ...
  2. ...
Expected:  <what should happen>
Actual:    <what happened>   Frequency: always / n of m
Evidence:  <links to logs / screenshots / trace>
--- HUMAN REVIEW GATE ---
Unconfirmed details / assumed severity / "Confirm before this is filed"

Guardrails

  • Never fabricate a reproduction step, log line, error message, or evidence link.
  • Severity and suspected-area are proposals — the triager and dev own the final call.
  • If it does not reliably reproduce, report that honestly rather than inventing a clean repro.
  • The report is a draft until a human confirms and files it.