skills.rest
JYeswak
JYeswakCOMMUNITY
Explore all skills by this author →
Website𝕏@ZestStreamGitHub

bug-repro

Reproduce reported bugs into minimal steps with environment evidence attached.

Updated Sep 11, 2026
Search Tags:#debugging#qa#regression#bug reproduction#issue verification#repro steps#environment evidence
One-click install
npx skills add https://github.com/JYeswak/grok_bot_playground --skill bug-repro-jyeswak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-repro
Source: https://github.com/JYeswak/grok_bot_playground/tree/main/plugin/skills/bug-repro
Command: npx skills add https://github.com/JYeswak/grok_bot_playground --skill bug-repro-jyeswak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Bug reports often arrive with vague steps, missing environment details, or unverified claims, forcing fixers to guess which build failed and how. This Skill turns a report into a minimal, evidence-backed reproduction where every step carries its command, input, and quoted observed output. ## Core Features & Use Cases - Evidence-backed repro steps: Each step records the exact command or action, its input, and the quoted observed output; unexecuted steps are labeled untried, never passing. - Minimal repro derivation: Steps are removed one at a time with re-runs after each removal, so the surviving set is proven minimal by still-failing runs. - Environment and verdict tracking: Every verdict names the build id, platform, OS, and config, plus one controlled variation run and a diff against any prior repro. - Use Case: A support engineer receives a ticket claiming a crash on export. The Skill re-executes the reporter's steps on the named build, strips the repro to three minimal steps, confirms the failure also occurs on the prior release, and hands the fixer a dated markdown file with verdict and evidence. ## Quick Start Ask the assistant to reproduce the bug described in ticket 4821 on build 2.4.1 and produce minimal repro steps with environment evidence.

Frequently Asked Questions about bug-repro

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

FAQPage Schema
How do I reproduce a bug report before fixing it?▼

Re-execute the reporter's steps literally on the exact named build, recording the command, input, and quoted observed output for each step. Then strip steps one at a time, re-running after each removal, until only the minimal failing set remains.

What makes a good minimal bug reproduction?▼

A good minimal repro numbers each step with its exact command or action, its input, and its quoted observed output, and names the build id, platform, OS, and config. Steps that were reasoned about but never executed are labeled untried, never passing.

Can this skill fix or patch the bug it reproduces?▼

No. The skill is strictly read-only: it reproduces and records, but never fixes, patches, commits, deploys, or changes any setting. A confirmed repro is evidence the fixer acts on, and only the owner's explicit approval authorizes any fix.

When should a bug be reported as cannot reproduce?▼

Report not-reproduced only when every step executed cleanly on the named build, with the steps run and outputs quoted. If some steps could not run, the verdict is blocked, naming what could not run and what would unblock it.

Why does a bug repro need the exact build and environment?▼

A verdict without a build id, platform, and config is not re-runnable and is demoted to a note rather than a finding. Output from one build is evidence about that build only and must never be presented as another build's behavior.

Related Skills

Explore More Software Engineering Skills→
4asaanAI4asaanAI

bug-report

Create structured bug reports with reproduction steps, environment details, and severity.

Community
Intermediate
saboteur-labssaboteur-labs

debug-issue

Diagnose software bugs by identifying root causes and delivering minimal, testable fixes.

Official
Advanced
dyyounggdyyoungg

sglang-bisect-ci-regression

Bisect CI commit windows to diagnose regressions from failure logs.

Community
Advanced
dyyounggdyyoungg

sglang-prod-incident-triage

Turn live SGLang serving incidents into replay-based debugging workflows.

Community
Advanced