agentleFS
Sn4kyGitSn4kyGit/qa-agent-blueprint/.claude/skills/bug-report/SKILL.md

bug-report

Skill2 starsChanged 7 days agoApache-2.0View on GitHub

Produce a bug report exactly per the active project's template. Use when a test finding becomes a bug ticket, "/bug-report" with a finding in hand, or "Bug melden", "mach ein Bug-Ticket draus". Not for triaging why a test failed — /failure-analysis first.

35 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-engine, team-polish 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

    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 13 projects that use this

  • CoralGameSkill

    team-polish

    Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.

    Also in 15 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 10 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 10 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 the project's report format is jira-cloud, remember: no pipe tables in ADF — see docs/rules/testing/jira-confluence.md.

    line 21

“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 — project-conformant bug report

Delegates composition to subagent bug-reporter, which never freelances the format — see .claude/agents/bug-reporter.md for its full process.

Steps

  1. Gather what's needed: the project key, the finding (repro steps actually executed, expected vs. actual, evidence file references), and severity.
  2. Invoke subagent bug-reporter with that context (including the routed product, if any). It reads the product's templates/bug-report.md when one exists, else projects/<KEY>/templates/bug-report.md, plus projects/<KEY>/PROJECT.md → "Reporting" for the severity/priority mapping, fills every template section, attaches evidence, and checks for duplicates.
  3. If the project's report format is jira-cloud, remember: no pipe tables in ADF — see docs/rules/testing/jira-confluence.md.
  4. Return the created/updated ticket key to the user (or to the calling skill, e.g. test-ticket).
  5. This skill writes no execution_summary.json of its own: when it ran inside a test run, the calling flow lists bug-report in that summary's skills_used (.claude/rules/core/evidence-policy.md) — actually used only.

What this skill does not do

It does not decide the test strategy or run the test — it packages an already-made finding. If no finding exists yet, run exploratory-testing or test-automation first.

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.