Claude Cursor opencode Skill

preview-manual-test

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.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download modem-dev-ossrules-public_files_kody_.agents_skills_preview-manual-test-d2b6775.zip · 1 KB

modem-dev/ossrules 29 1 forks MIT Updated 5d ago

Part of modem-dev/ossrules — 39 skills

Install

skills CLI npx skills add https://github.com/modem-dev/ossrules/tree/main/public/files/kody/.agents/skills/preview-manual-test

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install modem-dev-ossrules@llmmart

Git git clone https://github.com/modem-dev/ossrules.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole modem-dev/ossrules collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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.

Files (ossrules)

SKILL.md 2.3 KB

---
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.
---

# Manual preview testing

Read
[`docs/contributing/preview-manual-testing.md`](../../../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`](../control-kody/SKILL.md) when you also need `doctor`,
local login, Feature Map lookup, or a `/health` SHA check:

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

## Command

```bash
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:

```bash
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

1. 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.