| name | preview |
| description | Stand up the project's live app and hand it to the user to try a change firsthand, then gate on their verdict before continuing. Use when the user asks to "preview the change", "let me try it", "spin up the app so I can test it", "set it up so I can poke at it", or before finalizing a UI/UX change that needs human eyes. |
Preview
Bring up the running app and let the user drive it themselves to judge the change, then act on their verdict.
Step 1: Determine Scope
Resolve what to preview using the first match:
- User-specified — the user says what to look at. Use that.
- PR — a PR URL or number is provided. Fetch its details and read the changed code.
- Conversation context — prior conversation contains recent work. Extract what changed, where it lives, and the expected behavior.
- App-level discovery — fresh context with no prior work. Examine entry points, routes, and the README to identify the app's core user-facing flows.
If the resolved scope has no user-visible surface to try (a CLI-only change, a library with no entry point, backend work with no UI to look at), present this message: "Nothing to preview — ." Then call update_plan to mark this step completed and continue with the next step of the active workflow.
Step 2: Determine Launch Approach
Check for a project-specific skill or plugin that launches the app, and use it if present. Otherwise use the fallback for the surface type:
- Web app → start the dev server; the access point is the local URL and port
- Desktop/native app → build and launch the app so its window is open
Step 3: Bring Up the Stack
Start backend services and frontend together — a frontend-only change still needs the backend running to be exercised. Build first if the project requires a build step.
Start long-running processes in a background shell and wait until each reports ready. Tail their logs in a background shell so backend errors and warnings surface while the user is trying the app.
If a required service cannot be stood up in this session (missing auth provider, external dependency, seed data), or a process fails to start or never reports ready, use request_user_input to surface the blocker and let the user choose how to proceed.
Step 4: Point the User at the Running App
Output as text:
- The access point — the local URL and port for a web app, or confirmation that the window is open for a native app
- What changed and where to look
- Any specific interaction worth checking
- When a verification pass preceded this hand-over, what it could not cover: paths needing real credentials, external services, or state unavailable in this session
Step 5: Verdict Gate
Use request_user_input to ask the user for their verdict after they have tried the app. Three options, with keeping the app running as the default:
- Looks good, keep it running — leave every process this skill started running so the user can keep using the app.
- Looks good, shut it down — stop every process this skill started.
- Needs changes — note what the user wants different, make the change, rebuild or refresh the running app so it is live, then repeat this step's gate. When the user's response or session context surfaces further open issues, resolve every known issue — fixing and re-verifying each — before re-asking the verdict; the gate re-fires only once no known issue remains.
Then call update_plan to mark this step completed and continue with the next step of the active workflow.
