Verify Openwork
Prove an OpenWork change works on the real product before calling it done.
Install
npx skills add different-ai/openwork --skill verify-openwork -g -a claude-code -y- Repository
- different-ai/openwork24.4k
- Category
- Git and review
- Updated
- 3d ago
- License
- See repository
- Context cost
- Lightabout 940 tokens
- Runs scripts
- No, instructions only
What it does
Prove an OpenWork change works on the real product before calling it done. Start the product, drive the change the way a user or client would, capture screenshots, and show the proof fails on dev and passes on your branch. Use before opening a PR, when a reviewer asks "show me", or when a core journey is red.
Verify OpenWork
A change is done when you have watched it work on the real product, not when it
compiles. The committed e2e suite is only the nine core journeys in
evals/journeys.ts; everything else is proved per PR and thrown away.
1. Pick the check
| The change is… | Prove it with |
|---|---|
| a server rule (permissions, isolation, validation, secrets) | an API test next to the code, e.g. ee/apps/den-api/test/api/*.api.test.ts (pnpm --filter @openwork-ee/den-api test:api) |
| a pure function or component logic | a colocated unit test |
| something a person or client does end to end | a proof: evals/proofs/<name>.proof.test.ts (write-a-spec) |
| one of the nine core journeys broke or changed | a step in that journey, evals/core/<journey>.e2e.test.ts |
2. Start the product
pnpm world up dev-app-web --detach -- --browser # this checkout in headless Chrome; prints webUrl and cdp
pnpm world down dev-app-web # when done
Use a desktop window only for desktop-shell changes (see drive-desktop-cdp).
Den needs MySQL and Redis on localhost (pnpm dev:den:mysql, or a local MySQL
via OPENWORK_EVAL_MYSQL_URL=mysql://root@127.0.0.1:3306).
3. Drive it and keep the evidence
- By hand while working:
drive-desktop-cdp(new session, send, wait, screenshot). - As a proof:
pnpm evals:e2e <name> --local; screenshots and the report land inevals/results/test-runs/<latest>/.
Drive the real user path. No internal setters, no test-only endpoints, no
reading app state; pnpm --dir evals lint:specs rejects those in proofs.
4. Show it fails without your change
A proof that passes on dev proves nothing about your change. Run it on both:
