just-vibeGeneral · apply by default
/repro
Create a minimal, reliable reproduction of a problem
Use to isolate an observable failure; debug diagnoses the cause, test-flaky owns order and timing nondeterminism, test-regression locks the reproduced case, and fix changes production behavior after the trigger is understood.
Make it your own.
In Claude Code, use the slash command and add your context. In Codex, select repro from the just-vibe skill picker, then send the same brief.
Version 0.11.0 also supports /jv repro, /just-vibe repro and /jv:repro in Claude. See shortcut setup and context examples.
/just-vibe:repro Create an isolated minimal reproduction of the double-submission bug./just-vibe:repro Reproduce an order-dependent test failure without copying production secrets./just-vibe:repro Describe a reproduction plan when the affected binary is unavailable.What the agent does
- Confirm the symptom and freeze input and environment identity.
- Reduce unrelated dependencies and data one dimension at a time while preserving the failure trigger.
- Include a negative control that removes the suspected trigger, and document exact run and reset steps.
Inputs
- failure report, expected behavior, and environment constraints.
Optional context: scope, references, constraints, successCriteria, environment, mode, budget.
Scope
- Reads
- Minimal reproducer in an agreed scratch/test location; not a product fix.
- Writes
- Apply: only the requested local changes and relevant isolated verification. Inspect/plan requests remain inspection/planning. External actions require their exact action and target in session authorization.
- Mode
- Apply; failure report, expected behavior, and environment constraints.
- Prerequisites
- Resolve the user brief and inspect the relevant project or supplied evidence. External capabilities are optional unless the selected action actually needs them.
Expected output
- Isolated reproduction fixture or script with exact run/reset steps, expected versus actual output, environment identity and required conditions.
How the work is checked
- A fresh isolated run reproduces the issue; removing the critical trigger makes the failure disappear.
When to stop or clarify
- Redact production data and secrets. If reduction changes the symptom, keep the last valid reproducer and report the limit.
Handling missing context
- Infer
- Resolve the named files, existing scripts, current task and earlier corrections from the conversation and repository.
- Assume
- Use the narrowest interpretation that completes a reversible local task; state a consequential assumption once.
- Ask
- Ask when competing targets or incompatible success conditions would change the result; continue independent inspection first.
Technical guidance
- Evidence
- Capture exact input, environment, revision and the observable failure oracle.
- Method
- Reduce dependencies and data while preserving the causal trigger; keep synthetic substitutes faithful to the failing boundary.
- Pitfall
- A smaller program with a different failure does not reproduce the original bug.
- Check
- Run from a clean isolated setup and show the same expected-versus-actual mismatch with bounded execution.
Situational decisions
When reducing the case removes the failure intermittently: Preserve the last reliable reproduction and quantify repeats instead of discarding timing evidence.
The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.