verify
/verify
Project override for verifying a change in this repository. Activates whenever you are about to confirm that a change actually works — "verify this", "does this work", "check the page renders", "confirm the dashboard loads", "test this in a browser" — or whenever you are about to tell the user you could not verify something locally. In this repo a real headless Chromium IS available via `launchBrowser()`, so browser-testable changes must be verified locally rather than deferred to CI.
- Author
- app-vitals ↗
- Repository
- shipwright ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Project override for verifying a change in this repository. Activates whenever you are about to confirm that a change actually works — "verify this", "does this work", "check the page renders", "confirm the dashboard loads", "test this in a browser" — or whenever you are about to tell the user you could not verify something locally. In this repo a real headless Chromium IS available via `launchBrowser()`, so browser-testable changes must be verified locally rather than deferred to CI.
Triggers from the description
Original author description
Project override for verifying a change in this repository. Activates whenever you are about to confirm that a change actually works — "verify this", "does this work", "check the page renders", "confirm the dashboard loads", "test this in a browser" — or whenever you are about to tell the user you could not verify something locally. In this repo a real headless Chromium IS available via `launchBrowser()`, so browser-testable changes must be verified locally rather than deferred to CI.
How it works
- The rule
- The local-verification path
- Browser-testable surfaces in this repo
- What this does not change
SKILL.md preview
---
name: verify
description: >-
Project override for verifying a change in this repository. Activates whenever you are about
to confirm that a change actually works — "verify this", "does this work", "check the page
renders", "confirm the dashboard loads", "test this in a browser" — or whenever you are
about to tell the user you could not verify something locally. In this repo a real headless
Chromium IS available via `launchBrowser()`, so browser-testable changes must be verified
locally rather than deferred to CI.
---
# Verify — project override for this repository
This repo ships its own headless Chromium. **Do not fall back to "I can't test this locally,
trust CI"** for a change on a browser-testable surface here. That framing is wrong in this
repository, and using it hides regressions until after a PR is open.
## The rule
Before claiming a change is unverifiable locally, check which case you are in:
| Situation | What to do |
|---|---|
| The change touches a browser-testable surface **in this repo** | Verify it locally with `launchBrowser()`. Do not defer to CI. |
| The executing environment genuinely lacks the capability | Say so explicitly, name the missing capability, then fall back to CI. |
| The change is in **another repo** without this capability | Fall back to CI — this skill's guarantee is repo-local. |
"Genuinely lacks the capability" means Playwright's chromium-headless-shell is not installed —
e.g. non-agent-image local dev where `bun install` did not pull browsers. It does **not** mean
"running headless", "no display", or "in a container". Those are all supported.
## The local-verification path
`launchBrowser()` lives in `@app-vitals/agent-runtime/browser` (`browser.ts` in the published runtime package) (added in
PW-1.2). It returns a Playwright `Browser` already configured for this repo's restricted
container `securityContext` — headless, `chromiumSandbox: false`, and
`--no-sandbox --disable-setuid-sandbox`. You do not need to configure any of that yourself.
```ts
import { launchBrowser } from "@app-vitals/agent-runtime/browser";
const browser = await launchBrowser();
try {
const page = await browser.newPage();
await page.goto("http://localhost:3460/dashboard");
await page.waitForSelector("[data-testid=…]");
// assert on rendered output, console errors, network failures
} finally {
await browser.close();
}
```
Always close the browser in a `finally` — a leaked Chromium process will hang the test run.
## Browser-testable surfaces in this repo
- `site/*.spec.ts` — the Astro marketing site (Playwright, run from `site/`, **not** part of
root `bun test`)
- `metrics/e2e/` — the metrics dashboard (`dashboard.e2e.ts`, served by `test-server.ts`)
- `admin/e2e/` — the admin console (`agents-page.e2e.ts`, `login-page.e2e.ts`)
A change to the server-rendered dashboard, the admin console UI, or the marketing site is
browser-testable. Verify it.
## What this does not change
This skill governs **how you verify**, not what tests you commit. The repo's test-layer
conventions still apply — tests land with the code, at the correct layer, in the same PR, with
the layer encoded in the filename (see `docs/testing.md`). Running a browser to confirm a
change works is not a substitute for landing the appropriate `*.e2e.ts` / `*.smoke.test.ts`
coverage.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · app-vitals/shipwright | 100 | MIT |
| yonatangross/orchestkit | 100 | MIT |
| yonatangross/orchestkit | 100 | MIT |
| NolwennD/gabier | 100 | Apache-2.0 |
| ericrisco/rsc-harness | 100 | MIT |
| sentimony/agentic-workflow | 100 | MIT |
| JoDi-27/JoDi-SDD | 100 | MIT |
| marcel-bich/marcel-bich-claude-marketplace | 100 | MIT |
| kdlbs/kandev | 100 | AGPL-3.0 |
Database snapshot: 13.11.2026 · package version b9255ef66334 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100playwright-verify
Verify a web app's behavior in headless Chromium with Playwright, and give a web project that check as `make e2e`. Use after changing a web UI, when asked to confirm a page works in a real browser, or when a web project has no browser check yet. Use it instead of an interactive… - 100wowsir
Test and drive websites with the `wowsir` headless browser CLI. Use when asked to check a web page or flow, verify a UI change in the browser, reproduce a frontend bug, or write or run a browser test. - 100browser-test-loop
Use to actually verify a web change in a real browser instead of assuming it works — click through a flow, catch console errors, check a form submits, confirm a fix on the page. Trigger when a UI change needs proof, a bug only reproduces in the browser, or the user asks to test,… - 100browser-test
Check that a feature works by walking its scenarios in a real browser and writing a pass/fail report with evidence. A recipe over `haven browser`: no test files, no browser commands of its own. Use when someone says 'browser test', 'verify this in the browser', 'walk the… - 90browser-verification
Proves UI changes in a real headless browser before reporting done: served-build preflight, deterministic waits, element screenshots, overflow, contrast and target size as numbers, no console errors. Use when asked to verify, screenshot or visually check a page, confirm a… - 100qa-screenshot
Screenshot a page (deploy preview or a dev server on localhost) in the sandbox's headless Chromium, look at it, and embed it in a task comment. Use to verify a visual change or record before/after evidence.