agentleFS
MohamedRamadanSalahMohamedRamadanSalah/claude-qa-toolkit/.claude/skills/bug-report/SKILL.md

bug-report

Skill0 starsChanged 17 days agoMITView on GitHub

Turn a rough description of a problem, error log, or screenshot into a professional, validated bug report ready to paste into Jira/Azure DevOps. Use when the user found a bug, wants to report a defect, or needs help writing a bug ticket.

35 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use team-level, setup-engine and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CoralGameSkill

    team-level

    Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.

    Also in 13 projects that use this

  • CoralGameSkill

    setup-engine

    Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.

    Also in 14 projects that use this

  • lilangMaxSkill

    asset-spec

    Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.

    Also in 11 projects that use this

  • lilangMaxSkill

    create-control-manifest

    After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and engine reference docs. More immediately actionable than ADRs (which explain why).

    Also in 11 projects that use this

  • +4 more from CoralGame
  • +4 more from lilangMax

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 33 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If reproduction steps or environment are missing, ask ONE short question covering all gaps.

    line 13

“Common” is measured: kept by at least 6 in 10 of the 33 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Bug Report Writer

The user is a tester who found a bug. They may describe it roughly, in broken English, or just paste an error/screenshot. Produce a complete, professional bug report. Follow this workflow EXACTLY.

Workflow (mandatory)

  1. Extract facts from what the user gave (steps, environment, exact error text, screenshots — Read any image they attached).
  2. If reproduction steps or environment are missing, ask ONE short question covering all gaps. If the user seems in a hurry, use placeholders like <build version> and mark them clearly.
  3. Write the report to a file bug-reports/<short-slug>.md using EXACTLY this template (keep every **Section:** header — the validator checks them):
**Title:** [Component] What fails + under which condition

**Environment:** OS / browser or device / app version / build / environment (QA, staging...)

**Severity:** Blocker | Critical | Major | Minor | Trivial
**Priority:** P1 | P2 | P3

**Preconditions:** state needed before the steps

**Steps to Reproduce:**
1. ...
2. ...

**Actual Result:** what actually happens — include the EXACT error text

**Expected Result:** what should happen, with requirement reference if known

**Reproducibility:** Always / Intermittent (x out of y tries)

**Attachments/Evidence:** screenshots, logs, video to attach

**Notes / Possible cause:** optional observations

Severity guide: Blocker = testing/usage cannot continue; Critical = major function broken, no workaround; Major = major function broken but workaround exists; Minor = small function/UI defect; Trivial = cosmetic.

  1. Validate your report (MANDATORY):
python .claude/skills/bug-report/scripts/validate_bug_report.py bug-reports/<short-slug>.md

Fix every ERROR and re-run until it prints OK. Try to fix WARN lines too. Never show the user an unvalidated report.

  1. Show the user the final report plus one line justifying the Severity/Priority you chose.

Rules: title must be specific and searchable ("Login button does nothing after session timeout on Chrome 126" — never "Login broken"). Facts only, no blame, no guesses stated as fact.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.