/fix

Make it your own.

In Claude Code, use the slash command and add your context. In Codex, select fix from the just-vibe skill picker, then send the same brief.

Version 0.11.0 also supports /jv fix, /just-vibe fix and /jv:fix in Claude. See shortcut setup and context examples.

What the agent does

1. Read the behavior contract, nearby callers and existing checks before inferring expected behavior from the defective implementation. Separate the reproduced trigger, intended result and compatibility requirements; record conflicting evidence instead of choosing whichever makes the patch easiest.
2. Trace the failing input through validation, state transitions and the observable result. Choose a focused change that corrects the cause and preserves neighboring valid behavior; distinguish missing, null, zero, false and empty values where the contract does.
3. Reproduce the original failure, apply the fix and run relevant checks with actual exit statuses. Where a regression test is warranted, derive its expected result independently from the contract and establish that it detects the defect rather than incidental setup failure.
4. For a multi-phase feature, fix, refactor or MVP, use the relevant phase contract in the composed-workflows guide. Keep simple work direct. Delegate only when authorized, and use the reviewed worker result and acceptance flow before dependent work. Offer the plan-review canvas only when browser feedback is useful or requested.

Inputs

• symptom, expected behavior, and reproduction context. Requires source and a reproducible case or reliable failure evidence.

Optional context: scope, references, constraints, successCriteria, environment, mode, budget.

Scope

Reads

Correct the demonstrated cause and nearby necessary behavior; no broad cleanup.

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; symptom, expected behavior, and reproduction context. Requires source and a reproducible case or reliable failure evidence.

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

• Trigger, contract evidence, causal location, focused patch, actual before/after checks and remaining uncertainty.

How the work is checked

• The original failure no longer occurs; a neighboring valid case stays correct.

When to stop or clarify

• If reproduction is unavailable, label hypotheses and investigate without presenting a speculative patch as a verified fix.

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

Establish actual versus expected behavior, reproducible trigger and first causal divergence.

Method

Create a discriminating regression, repair the owning boundary and check adjacent legitimate behavior.

Pitfall

Editing the last visible exception or weakening the assertion can hide the root defect.

Check

Demonstrate the original failure in isolation where feasible and verify the fix without relying on unrelated worktree changes.

Situational decisions

When the written contract disagrees with the current fallback or coercion: Treat the discrepancy as part of the bug investigation. Check callers and compatibility evidence; do not encode the old fallback into a new test merely because it already exists.

When failure cannot be reproduced: Compare environments and choose a discriminating experiment. Label an unverified patch as partial and state which observation would establish the result.

The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.

Keep exploring