/vercel-preview

Make it your own.

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

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

What the agent does

1. Resolve the intended project and commit, and inspect prerequisites.
2. Reuse a matching deployment where suitable; create one only when requested.
3. Verify identity, URL, access protection, routes and representative behavior.

Inputs

• branch/PR, project, revision, and preview goal. An explicit create-preview request authorizes that preview deployment.

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

Scope

Reads

Preview environment only, including authorized smoke checks.

Writes

Inspect/plan: inspect or propose; save requested artifacts only. Apply: make the requested changes or execute the requested operation within its resolved target and limits. Local preparation does not authorize live, remote, destructive or paid actions; existing explicit session authorization still applies.

Mode

Inspect an existing preview or plan a proposed one; apply for requested preview configuration or creation.

Prerequisites

Exact team/project/environment and deployment/revision when applicable; read access to relevant configuration/logs. Verify installed CLI/API support and framework behavior during implementation. Never print environment values or infer promotion authorization from a preview request.

Expected output

• Preview plan or actual URL and deployment ID with the exact revision, access requirements and observed smoke-check results.

How the work is checked

• The preview serves the intended commit; a protected preview is reported as access-restricted rather than broken without evidence.

When to stop or clarify

• No promotion, production-domain changes, or unsolicited sharing. Check for existing deployment after uncertain creation.

Handling missing context

Infer

Read the linked project, team, framework, environment and deployment SHA from local config and supplied deployment evidence.

Assume

Diagnose locally with existing build scripts when deployment access is missing; do not infer a production target from a preview URL.

Ask

Resolve a missing deployment/team/environment before the dependent remote operation; names and scope suffice without exposing environment values.

Technical guidance

Evidence

Resolve branch/head SHA, existing matching deployments and access-protection expectations.

Method

Reuse an appropriate existing preview or create the requested one; check nested routes, APIs and assets at its immutable deployment identity.

Pitfall

Anonymous 401/403 from protection is not necessarily app failure; a branch alias may advance while checks run.

Check

Record deployment ID, SHA, URL and actual route observations, including unavailable protected checks.

Situational decisions

When a deployment request times out: Query for the intended revision before retrying; distinguish a protected URL from an unhealthy app.

When the request is for local preparation or implementation: Prepare requested preview configuration locally; submitting a preview requires the intended project/account and source revision, with no implicit production promotion.

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