/orient

Make it your own.

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

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

What the agent does

1. Run the bundled inspector with the selected project root. Read relevant ancestor and discovered project instructions, manifests, scripts, and representative entry points.
2. When the user names a goal, explain how it fits the actual project; otherwise summarize each package's role and entry points. List commands with their package directories; run only side-effect-free checks after reading the script body, and label every other command discovered rather than verified.

Inputs

• repository or directory plus optional onboarding goal. Requires readable project files; runtime checks are optional.

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

Scope

Reads

Stack, entry points, package boundaries, instructions, and documented commands; no setup or dependency installation.

Writes

No source changes in inspect/plan. Save only requested planning artifacts. A separately requested repair uses the relevant implementation workflow.

Mode

Inspect; repository or directory plus optional onboarding goal. Requires readable project files; runtime checks are optional.

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

• Project orientation with file links, conventions and unknowns, plus an entry-point table (path, role, caller, verification command, unresolved assumption) that labels each command discovered or verified.

How the work is checked

• A monorepo yields package-specific commands; stale README instructions are identified rather than repeated as working.

When to stop or clarify

• Unreadable roots or ambiguous projects produce a targeted blocker; never claim the application runs without evidence.

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 bounded manifests, entry points, scripts, workspace layout and applicable project instructions.

Method

Distinguish declared stack from observed runnable commands; follow a representative entry point to its owner.

Pitfall

A package script's name does not prove it works, and importing configuration can execute code during inspection.

Check

Cite the source of stack/build claims and identify commands actually executed versus merely discovered.

Situational decisions

When multiple packages or stale documentation: Identify each package's role and distinguish configured commands from commands actually exercised.

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