CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

qa-bug-reporting

Write, dedupe, and rank defect records with minimal repro steps, expected-versus-actual results, sanitized evidence, reproducibility counts, and root-cause confidence. Use whenever a test fails or an anomaly is found.

67

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Bug Reporting

Procedure

  1. Reproduce at least twice from a clean state. Record failures over attempts.
  2. Minimize the steps to the shortest path that still fails.
  3. Fill templates/bug-report.md. The title states the wrong outcome ("Repeat audits by signed-in members never start"), not the component.
  4. Attach sanitized evidence: screenshot, trace, response, and run ID. Redact tokens, cookies, emails, and keys.
  5. Root cause: mark CONFIRMED only with a code or log trace. Otherwise SUSPECTED or UNKNOWN.
  6. Reachability: confirm the code path is live in this build (pattern F4).
  7. Dedupe: one record per distinct root cause, with symptoms linked.
  8. Rank by severity, then customer reach.

Exit criteria

Every FAIL in the matrix links to a bug record or a test-defect record.

Repository

itsablabla/qa-bug-agent-skills

Path

skills/qa-bug-reporting/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.