reproduce-first

What problem does it solve?

Prevents accidental, unverified fixes by ensuring every bug-fix session starts by reproducing the user-visible failure with a failing end-to-end specification.

Core Features & Use Cases

• Step-1 Bug Understanding (Context Gathering): Parses an issue id (e.g., Linear OPE-123) and pulls full context via MCP functions, or asks targeted clarifying questions when given free-text.
• Step-2 Spec Selection or Proposal: Checks for an existing E2E spec in the correct test suite, proposes a minimal new spec when none exists, or asks before extending an adjacent spec when one seems incomplete.
• Step-3 Red Confirmation Workflow: Requires that the selected or newly added spec fails (RED) via the project’s test runner before any fix code is written.
• Step-4 Minimal Fix & Step-5 Green Verification: Applies the smallest possible code change to make the spec pass (GREEN), reruns the same spec to confirm, and optionally checks adjacent tests to reduce regressions.
• Use Case: When a user reports a wrong UI behavior or regression in an application flow, start this skill to produce a reliable failing E2E test that proves the bug exists before changing implementation code.

Quick Start

Run reproduce-first with the issue id or a brief description of the bug so the workflow can produce (or locate) a spec that reproduces the failure.