菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/kentcdodds/kody --skill preview-manual-test命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
How to run and test kody's multi-worker local dev (origin kody worker + kody-platform + kody-runtime + kody-jobs secondary configs), including known wrangler multi-config pitfalls (secondary worker env-name suffix, remote AI binding, .env secrets not propagated) and how to verify runtime-worker forwarding.
Babysit a PR: iterate with AI reviewers and CI until green, get it ready, optionally squash-merge as Kody and watch the deploy, then send a Discord summary. Medium risk waits for AI reviewer(s) and addresses valid feedback. Use when a pull request needs to be shepherded to done.
Coordinate a fleet of cloud agents across separate environments for large multi-track programs (migrations, purges, upgrades). The conductor audits, partitions, spawns one agent per track, monitors, and QAs — but implements nothing. Use only when work needs multiple environments; otherwise load orchestrate or implement directly.
正在显示 SKILL.md
| name | preview-manual-test |
| description | 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. |
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.
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
--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.
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.
computerUse subagent./login with the seed credentials. Button label is Sign in.GET /mcp is 401 without OAuth; /admin is 403 (seed account is not admin).
Neither is a regression.