Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Development

magpie-issue-reproducer

For a single `<issue-tracker>` issue identifying a code-level bug, extract the reporter's example code from the issue body, adapt it to run on the current `<default-branch>`, execute via `<runtime>`, and compose a `verdict.json` describing the observed behaviour vs the expected failure. Read-only on the tracker — produces evidence, never posts. Invoked by `issue-triage` and `issue-reassess`; can also be run standalone.

apache · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add apache/magpie --skill magpie-issue-reproducer

About this skill


SPDX-License-Identifier: Apache-2.0

https://www.apache.org/licenses/LICENSE-2.0

name: magpie-issue-reproducer family: issue mode: Meta description: | For a single <issue-tracker> issue identifying a code-level bug, extract the reporter's example code from the issue body, adapt it to run on the current <default-branch>, execute via <runtime>, and compose a verdict.json describing the observed behaviour vs the expected failure. Read-only on the tracker — produces evidence, never posts. Invoked by issue-triage and issue-reassess; can also be run standalone. when_to_use: | Invoke when the user names a single issue and says "reproduce this", "check whether this still fails on master", "run the example from the bug report", or "see if this is fixed". Also when a sibling skill says "reproducer required" for an issue in its candidate set. Skip when the issue does not carry runnable example code — use issue-triage to assess instead. capability: capability:reassess license: Apache-2.0

issue-reproducer

Use this skill when the job is to take an issue-described problem and actually run it: find the reproducer code, work out what shape it's in, adapt it to a runnable form, and execute it against the current <default-branch> and the project's runtime with enough evidence captured that a maintainer can trust the verdict without redoing the work.

This skill is the load-bearing piece for both single-issue triage (when a stronger-than-eyeballed reproduction is wanted) and bulk reassessment campaigns. It doesn't speak about workflow, batch processing, or hand-back — those belong to the calling skills:

  • issue-triage — invokes this skill at the "attempt reproduction on <default-branch>" step when a classification hinges on runtime evidence.
  • issue-reassess — bulk reassessment campaign; calls this skill for every issue in the candidate set.
  • issue-fix-workflow — when the reproducer adapts cleanly to a regression test, the fix-workflow skill takes the adapted form as its starting point.

Golden rules

Golden rule 1 — never fabricate. "The reporter described X happening; I'll write code that does X." That is the agent doing the reporter's job. If the description is prose-only and no attachment helps, classify cannot-run-extraction and stop. The reporter's specific code is what makes a reproduction trustworthy; an agent-written stand-in is a different exercise (and a different verdict). The full anti-fabrication discipline lives in extraction.md.

Golden rule 2 — inventory everything, run every case. Reporters frequently post simplified reproducers in comments after the initial description, and may follow up with additional cases that exercise different symptoms of the same root cause. Inventory every code block in the description and every comment and every attachment; when distinct reproducers exist, run each and record per-case outcomes — not just the headline. The cases array in verdict.json (see verdict-composition.md) carries per-case state for multi-case issues.

Golden rule 3 — bounded runs only. Timeout (60s default; raise per-issue if the reporter notes long-running behaviour). Without a timeout, one bad issue burns hours. Classify as timeout if hit. See runtime-recipes.md for the full posture.

Golden rule 4 — capture both streams. Many reproducers print the bug indicator (stack traces, error messages, "expected X got Y") to stderr. Capture stdout + stderr + exit code + runtime. Record the command verbatim.

Golden rule 5 — read-only on tracker state. This skill produces evidence; it does not post, transition, close, or modify anything on <issue-tracker>. Posting / transitioning belongs to issue-triage and sibling skills.

Golden rule 6 — no working-tree leaks between issues. When running many reproducers in sequence, reset between issues. A file written by issue A's reproducer that issue B's run picks up corrupts verdicts in ways that are hard to spot. See runtime-recipes.md for hygiene patterns.

Golden rule 7 — don't over-claim from one environment. A clean run on the operator's laptop may be environment-luck — locale, charset, default JDK or interpreter, file-encoding defaults all bite. Where the verdict is passes or fixed-on-master, qualify with the environment that produced the pass; don't generalise.

Golden rule 8 — reporter code is hostile until proven otherwise. The reproducer is attacker-controlled input that this skill executes. A malicious reporter — or an issue body carrying an invisible HTML-commented payload — can ship code that exfiltrates credentials, writes outside the scratch tree, or phones home the moment <runtime> is invoked. Two non-negotiable consequences: (1) the run happens only inside the framework's credential-isolation setup (Step 0 verifies it; see docs/setup/secure-agent-setup.md), and (2) a human expl

Read the complete source ↗