How do I install the Preview Manual Test skill?

Run npx skillmds@latest add kentcdodds/preview-manual-test in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Preview Manual Test safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Preview Manual Test?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Preview Manual Test free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Preview Manual Test?

kentcdodds (@kentcdodds) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Preview Manual Test by kentcdodds — Agent Skill

Name: Preview Manual Test
Author: kentcdodds

File contents

Manual preview testing

Read docs/contributing/preview-manual-testing.md. Do not improvise gh comment scraping, local E2E against the preview URL, or raw D1 seeding of preview resources.

Prefer control-kody when you also need doctor, local login, Feature Map lookup, or a /health SHA check:

npm run control-kody -- preview -- --request 'GET /onboarding.json' --check /onboarding/step-2

Command

npm run preview:manual-test

On medium or high risk, do not stop at the default health/login smoke. The seed user (me@kentcdodds.com / ilikecode, username user-me) has no secrets, packages, or jobs until you create them. Script that data and the assertions as the same logged-in user:

npm run preview:manual-test -- \
  --request 'POST /onboarding/checklist-dismiss.json {}' \
  --request 'GET /onboarding.json' \
  --check /onboarding/step-2

--request spec: METHOD /path [status] [json-body] (default success: 2xx). Use the JSON APIs the UI uses (/account/*.json in packages/worker/universal/routes.ts). --json includes session.cookieHeader; --cookie-file writes it for follow-up curl.

--pr, --url, --no-wait, --skip-login, --help as documented.

When

After the PR is ready for review (drafts and forks have no preview) and you have pushed the commits you want to exercise. Typical triggers: visual-recap risk is medium (extends) or high (adds); auth, workers, or deploy-path behavior changed; the user asked to try the preview.

This does not replace npm run validate.

After the scripted session

Open the printed URL. On Cloud Agents, use the computerUse subagent.
Sign in at /login with the seed credentials. Button label is Sign in.
Confirm the data you created and exercise the UI this PR changes. Stay on the preview origin.
Record what you saw on the PR.

GET /mcp is 401 without OAuth; /admin is 403 (seed account is not admin). Neither is a regression.

---name: preview-manual-testdescription: Discover, wait for, sign in, create specific user data, and assert a PR preview deploy. Use on medium or high risk PRs, after pushing a ready-for-review PR, or when the user asks to test the preview URL.---# Manual preview testingRead[`docs/contributing/preview-manual-testing.md`](../../../docs/contributing/preview-manual-testing.md).Do not improvise `gh` comment scraping, local E2E against the preview URL, orraw D1 seeding of preview resources.Prefer [`control-kody`](../control-kody/SKILL.md) when you also need `doctor`,local login, Feature Map lookup, or a `/health` SHA check:```bashnpm run control-kody -- preview -- --request 'GET /onboarding.json' --check /onboarding/step-2```## Command```bashnpm run preview:manual-test```On **medium or high risk**, do not stop at the default health/login smoke. Theseed user (`me@kentcdodds.com` / `ilikecode`, username `user-me`) has **no**secrets, packages, or jobs until you create them. Script that data and theassertions as the same logged-in user:```bashnpm run preview:manual-test -- \ --request 'POST /onboarding/checklist-dismiss.json {}' \ --request 'GET /onboarding.json' \ --check /onboarding/step-2````--request` spec: `METHOD /path [status] [json-body]` (default success: 2xx).Use the JSON APIs the UI uses (`/account/*.json` in`packages/worker/universal/routes.ts`). `--json` includes`session.cookieHeader`; `--cookie-file` writes it for follow-up `curl`.`--pr`, `--url`, `--no-wait`, `--skip-login`, `--help` as documented.## WhenAfter the PR is **ready for review** (drafts and forks have no preview) and youhave pushed the commits you want to exercise. Typical triggers: visual-recaprisk is **medium** (`extends`) or **high** (`adds`); auth, workers, ordeploy-path behavior changed; the user asked to try the preview.This does not replace `npm run validate`.## After the scripted session1. Open the printed URL. On Cloud Agents, use the `computerUse` subagent.2. Sign in at `/login` with the seed credentials. Button label is **Sign in**.3. Confirm the data you created and exercise the UI this PR changes. Stay on the preview origin.4. Record what you saw on the PR.`GET /mcp` is 401 without OAuth; `/admin` is 403 (seed account is not admin).Neither is a regression.

Frequently asked questions

Preview Manual Test