skills.rest
mattjefferson
mattjeffersonCOMMUNITY
Explore all skills by this author →
Website𝕏@mjeffersonGitHub

bug-reproduction-validator

Reproduce reported steps and classify outcomes as confirmed bugs or errors.

Updated Aug 23, 2026
Search Tags:#debugging#validation#quality-assurance#reproduction#bug#issue-triage
One-click install
npx skills add https://github.com/mattjefferson/open-compound-engineering --skill bug-reproduction-validator-mattjefferson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-reproduction-validator
Source: https://github.com/mattjefferson/open-compound-engineering/tree/main/skills/bug-reproduction-validator
Command: npx skills add https://github.com/mattjefferson/open-compound-engineering --skill bug-reproduction-validator-mattjefferson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically validates bug reports to determine if reported behavior is a genuine defect, reducing wasted effort on false positives.

Core Features & Use Cases

  • Reproduce reported steps with a structured, repeatable process.
  • Gather environment data, logs, and evidence for verdicts.
  • Classify outcomes as Confirmed Bug, Not a Bug, or Environmental/Data/User Error.

Quick Start

Instruct the agent to reproduce the reported steps and document the verification outcome.

Frequently Asked Questions about bug-reproduction-validator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a bug report to see if it reflects a real defect?▼

To validate a bug report, systematically reproduce the described steps, compare observed outcomes to expected behavior, and classify the result as a Confirmed Bug, Not a Bug, or Environmental Error.

What is the best way to reproduce software bugs across different environments and teams?▼

Reproducing software bugs requires applying a structured workflow that captures reproduction steps, environment context, and logs, running the process multiple times to ensure conformance to the project's intended behavior.

How do I document findings and root cause after triaging an issue?▼

Document findings and root cause by capturing environment data, logs, and evidence during the reproduction process, then record a final verdict with recommended actions based on the expected behavior comparison.

How do I classify bug triage outcomes to reduce wasted effort on false positives?▼

Classify bug triage outcomes by comparing observed reproduction results against expected behavior, categorizing them as Confirmed Bug, Not a Bug, or Environmental/Data/User Error to eliminate false positives.

Do I need specific logging tools to verify a reported issue?▼

You do not need specific logging tools to verify a reported issue, but the validation process requires capturing environment data, logs, and evidence from your current setup to support the final verdict.

Related Skills

Explore More Software Engineering Skills→
mediar-aimediar-ai
1.6k

Terminator Issue Reporter

Generate structured GitHub issues for Terminator failures with logs and reproduction steps.

Official
Advanced
danieljformandanieljforman

ceos-ids

Identify root causes and assign owner To-Dos with due dates.

Community
Advanced
ViindooViindoo
7

odoo-qa-suite

Automate QA test plans, deployment checklists, and bug severity classification for Odoo modules.

Official
Advanced
jshsakurajshsakura
22

ui-ux-tester

Validate UI/UX flows end-to-end and report defects with reproduction steps.

Community
Advanced