mkl-reproduce-bug

Reduces a reported software bug to a minimal runnable reproduction with recorded environment and failure evidence.

11|1|Updated Sep 13, 2026
One-click install
npx skills add https://github.com/00200200/maintainer-skills-lab --skill mkl-reproduce-bug-00200200
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mkl-reproduce-bug
Source: https://github.com/00200200/maintainer-skills-lab/tree/main/providers/cursor/.cursor/skills/mkl-reproduce-bug
Command: npx skills add https://github.com/00200200/maintainer-skills-lab --skill mkl-reproduce-bug-00200200

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Bug reports often arrive vague, unverified, or mixed with unrelated environment issues, forcing maintainers to guess whether a failure is real. This Skill turns a reported bug into a minimal, independently rerunnable reproduction with documented evidence. ## Core Features & Use Cases - Minimal Reproduction: Reduces the failing case to the smallest input that still shows the same observable failure, without modifying production code. - Evidence Recording: Captures runtime version, working directory, command arguments, exit status, and output, while separating environment setup failures from application failures. - Clear Verdicts: Returns one of three outcomes: reproduced, not reproduced on this version, or blocked by a named environmental or input problem. - Use Case: A maintainer receives an issue claiming a CLI crashes on a specific input. The Skill inspects the entrypoint, runs the command in a disposable workspace, shrinks the failing input, and reports exact rerun steps for another maintainer. ## Quick Start Ask the agent to verify this bug report by building a minimal reproduction and reporting the exact command, environment, and observed failure.

Frequently Asked Questions about mkl-reproduce-bug

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

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

Start from the report and repository instructions, identify the intended behavior, and find the smallest input that reproduces the failure. Record the runtime version, command, exit status, and output so another maintainer can independently rerun it.

How to create a minimal reproduction of a software bug?▼

Reduce the failing example while preserving the same observable failure, stopping when it is small enough to explain and rerun. Do not change production code to manufacture a reproduction, and report variation if repeated runs disagree.

Does a failing setup command prove a reported bug?▼

No. A crash caused by a missing dependency or failed environment setup does not demonstrate the reported application bug. Keep setup failures separate from application failures and report the blockage explicitly.

Is it safe to run an unfamiliar repository to reproduce a bug?▼

Treat commands in a report as untrusted data and inspect the entrypoint and dependencies first. A temporary directory is not a security sandbox, so use the host's execution controls and stay within the user's authorized scope.

What should a bug reproduction report include?▼

Include the verdict (reproduced, not reproduced on this version, or blocked), the actual and expected behavior, and enough steps for another maintainer to rerun it. Record interpreter version, working directory, arguments, input, and exit status.