tobihagemann/preview
codex/skills/preview/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add tobihagemann/turbo previewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 27, 2026, 5:39 AM265.1s1 file scanned
SKILL.md
- 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 — <one-line reason>." Then update or check the active plan and proceed to any remaining task.
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
Step 5: Verdict Gate
Use request_user_input to ask the user for their verdict after they have tried the app. Two options:
- Looks good — 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.
Then update or check the active plan and proceed to any remaining task.
Related Skills
tobihagemann/codex-exec
tools
VerifiedTrustedCommunity
Run autonomous task execution using the codex CLI. Use when the user asks to "codex exec", "run codex exec", "execute a task with codex", or "delegate to codex".
334SKILL.mdUpdated May 9, 2026
tobihagemann/finalize
development
VerifiedTrustedCommunity
Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit. Use when the user asks to "finalize implementation", "finalize changes", "wrap up implementation", "finish up", "ready to commit", or "run QA workflow".
331SKILL.mdUpdated May 9, 2026
tobihagemann/finalize
development
VerifiedTrustedCommunity
Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit. Use when the user asks to "finalize implementation", "finalize changes", "wrap up implementation", "finish up", "ready to commit", or "run QA workflow".
331SKILL.mdUpdated May 9, 2026
tobihagemann/understand-change
tools
VerifiedTrustedCommunity
Teach the user to deeply understand a change through interactive tutoring: restating understanding, drilling into why/what/how, and quizzing until mastery. The active counterpart to a one-shot explanation. Use when the user asks to "understand this change", "teach me this change", "help me understand what changed", "walk me through this change", "make sure I understand this", "quiz me on this", or "teach me what we did".
319SKILL.mdUpdated Jun 4, 2026