qa-bug-repro
Bug reproduction workflow: 1 skill (bug-report-template) and 9 agents (bug-report-from-recording, bug-repro-builder, crash-stack-trace-analyzer, defect-clusterer, defect-pipeline-runner, defect-trend-narrator, escape-defect-analyzer, failure-classifier, test-failure-debugger).
Install this plugin
/plugin install qa-bug-repro@testland-qaPart of role bundles: qa-starter, qa-role-manual-tester
qa-bug-repro
Bug reproduction workflow: extracts bug reports from Playwright traces / HARs, builds minimal failing tests from issue reports, authors and reviews bug reports (including CI-failure-to-spec conversion), triages CI failures, and runs the weekly defect-review pipeline.
Components
| Type | Name | Description |
|---|---|---|
| Skill | bug-report-template | Build a triageable bug report from raw notes; convert a CI failure record into a classified, ready-to-file spec; audit any report against the pre-filing review checklist. |
| Skill | ci-failure-triage | Decides what kind of failure a red test is before anyone fixes it: seven signals, an ordered first-match-wins rule set, and a verdict that records which alternatives were rejected and why. |
| Skill | defect-escape-taxonomy | Classifies a production escape into test, process, or tooling gap by the earliest layer that should have caught it, stated as a property of the system and never of a person. |
| Agent | bug-report-from-recording | Action-taking: read a Playwright trace.zip (or HAR + console + screenshot) and emit a filled bug-report-template with verbatim error messages, reconstructed repro steps, and trace-derived environment block. |
| Agent | bug-repro-builder | Action-taking: turn a bug report into a minimal failing test (unit / integration / component / e2e) or a minimal-repro repository. |
| Agent | defect-pipeline-runner | Weekly defect-review pipeline in one agent: cluster the backlog by fingerprint, narrate the trend (Pareto + WoW deltas + escape rate), classify production escapes as test / process / tooling gaps. |
Install
/plugin marketplace add testland/qa
/plugin install qa-bug-repro@testland-qaSkills
bug-report-template
Builds a well-formed bug (defect) report from raw observation notes - fills in summary, environment, steps to reproduce, expected vs actual, and severity rationale - and validates that each field has the load-bearing content reviewers and engineers need to triage. Also converts a single test-failure record (JUnit XML, Allure JSON, pytest log, Playwright report) into a classified, ready-to-file bug spec, and provides the adversarial review checklist that gates a report before it enters the tracker (required fields, single-description title test, severity-priority independence, reproduction quality). Use when a stakeholder reports a problem informally, when a CI failure artefact needs to become a triageable report, or when a drafted report needs a pre-filing quality audit.
ci-failure-triage
Decides what kind of failure a red CI test is before anyone starts fixing it. Extracts seven failure signals from the runner output, stack trace, run history, and environment metadata, then walks an ordered first-match-wins rule set to exactly one verdict: flaky-known, environment-drift, defect, timeout, flaky-pre-incident, or flake-of-unknown-cause. Emits the verdict together with the alternatives that were rejected and the specific condition each one failed, so the triage decision is auditable rather than asserted. Use when a test has just gone red and the next action depends on whether the cause is a product defect, a non-deterministic test, or drifted infrastructure.
defect-escape-taxonomy
Classifies a defect that reached production into one of three root gap categories (test gap, process gap, tooling gap) and one of thirteen sub-patterns, applying the earliest-layer rule: the category is the earliest layer that should have caught the defect, expressed as a property of the system and never of a person. Each sub-pattern carries the typical prevention fix, so the finding names an actionable class of gap. Rejects blame language and generic prevention assets such as 'add more tests'. Does not triage or prioritize the defect, does not write the missing test, and does not run a full incident postmortem. Use when a defect has been confirmed in production and the team needs to name which class of gap let it through before deciding what to build.
Agents
bug-report-from-recording
Action-taking agent that ingests a Playwright trace.zip (and/or a HAR file plus console logs and screenshots) and emits a structured bug report matching the `bug-report-template` schema - verbatim error messages, repro steps reconstructed from the recorded actions, environment block populated from the trace metadata, expected-vs-actual filled from the recorded assertions and observed responses. Distinct from `bug-report-template` (which fills the same template from chat / voice / informal text) and from `bug-repro-builder` (which converts the report into a failing test). Use when a manual tester or CI run captured a Playwright trace and the team needs a triageable issue without round-tripping for missing fields.
bug-repro-builder
Action-taking agent that turns a bug report into a minimal failing test (or, when the bug needs more context than a unit test allows, a minimal repro repository). Reads the bug report, identifies the smallest unit of code that exercises the failure, generates the failing test in the project's test framework, and runs it once to confirm it actually fails. Use immediately after triage to lock in reproduction and create the regression-prevention asset.
defect-pipeline-runner
Runs the full weekly defect review as one agent, in three internal stages: (1) clusters the backlog into root-cause groups by stack-trace top frame, normalized error + route, and component/severity fingerprints; (2) narrates the trend - Pareto breakdown of root-cause categories, week-over-week deltas, top-3 movers, escape rate; (3) classifies each production escape as a test gap, process gap, or tooling gap per the escape taxonomy - then assembles one consolidated report for the QA manager or lead. Read-only: enforces required inputs per stage and refuses to proceed when upstream data is missing. Use when a QA manager or lead wants a single, end-to-end weekly defect review from a tracker export or a directory of bug reports.