just-vibeGeneral · plan by default
/learn
Extract a reusable lesson from completed work for review
Use to extract a candidate reusable lesson from observed work; remember persists an authorized convention, teach instructs the user on a topic and explain describes existing code.
Make it your own.
In Claude Code, use the slash command and add your context. In Codex, select learn from the just-vibe skill picker, then send the same brief.
Version 0.11.0 also supports /jv learn, /just-vibe learn and /jv:learn in Claude. See shortcut setup and context examples.
/just-vibe:learn Extract a scoped lesson from this retry incident for review, not adoption./just-vibe:learn Extract a lesson from a flaky test caused by shared state./just-vibe:learn Analyze a failed session with no verified fix; keep causes and lessons provisional.What the agent does
- Link the actual failure trigger to the successful intervention, separating generalizable conditions from accidents.
- Test the lesson against a plausible counterexample and state when it should not apply.
Inputs
- completed task or incident and supporting evidence.
Optional context: scope, references, constraints, successCriteria, environment, mode, budget.
Scope
- Reads
- Extract a reusable lesson for review; no automatic permanent rule installation.
- Writes
- No source changes in inspect/plan. Save only requested planning artifacts. A separately requested repair uses the relevant implementation workflow.
- Mode
- Plan; completed task or incident and supporting 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
- Proposed lesson recorded as trigger, action, evidence and exceptions, with a suggested adoption scope.
How the work is checked
- A transient outage does not become a universal coding rule; an applicable repeated failure yields a bounded recommendation.
When to stop or clarify
- Missing evidence limits the output to a hypothesis. Persist behavioral changes only when the user requests adoption.
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
- Inspect a completed task's actual failure, correction and verified result.
- Method
- Extract a scoped reusable lesson with its trigger and limits; save only when requested in the approved location.
- Pitfall
- Generalizing one incident into an unconditional global rule can harm unrelated work.
- Check
- Check the lesson against both the triggering case and a nearby case where it should not apply.
Situational decisions
When evidence comes from one transient incident: Keep the lesson conditional and propose a validation case instead of a universal rule.
When the user adopts the lesson: Project conventions go through remember; a workflow-specific behavior change goes through assist feedback, or learn propose for a conditional change, quoting the user adoption message. Review learned candidates with learn status, then learn approve or learn reject.
The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.