← ClaudeAtlas

issue-reproducerlisted

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/airflow-steward · ★ 19 · Data & Documents · score 80
Install: claude install-skill apache/airflow-steward
<!-- SPDX-License-Identifier: Apache-2.0 https://www.apache.org/licenses/LICENSE-2.0 --> <!-- Placeholder convention (see ../../../AGENTS.md#placeholder-convention-used-in-skill-files): <project-config> → adopter's project-config directory <issue-tracker> → URL of the project's general-issue tracker <upstream> → adopter's public source repo <default-branch> → upstream's default branch (master vs main) <runtime> → recipe for invoking the project's runtime (resolves from <project-config>/runtime-invocation.md) Substitute these with concrete values from the adopting project's <project-config>/ before running any command below. --> # 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`](../issue-triage/SKILL.md) — invokes this skill at the *"attempt reproduction o