agentleFS
app-vitalsapp-vitals/shipwright/.claude/skills/verify/SKILL.md

verify

Skill16 starsChanged 24 days agoMITView on GitHub

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.

189 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use instinct-export, instinct-import and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • TheKREATORSSkill

    instinct-export

    Export instincts from project/global scope to a file

    Also in 3 projects that use this

  • TheKREATORSSkill

    instinct-import

    Import instincts from file or URL into project/global scope

    Also in 3 projects that use this

  • AviadPSkill

    risk-assess

    Assess the risk and blast radius of a proposed code change before implementing it. Evaluates CI impact, framework-wide vs localized scope, rollback path, and identifies blindspots. Use when user says "what's the risk", "is this safe", "assess the impact", "risk assess", "blast radius", or before applying framework-wide or CI-affecting changes. Do NOT use for code quality review (use code-quality) or plan validation (use design-validator).

    Also in 3 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 6 projects that use this

  • AaravChadhaSkill

    secure

    Security review with a confidence gate - a finding exists only with a concrete exploit scenario and a high/medium/low confidence rating; everything else goes to a worth-hardening list, never inflated. Sweeps five surfaces: auth gates, secrets hygiene, injection and unsafe sinks, unsafe deserialization/crypto/transport, and LLM tool-use trust boundaries. Reports only, never fixes. Use when the user asks for a security review or to check vulnerabilities, secrets, or auth.

    Also in 3 projects that use this

  • ArvorCoSkill

    specify

    Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.

    Also in 10 projects that use this

  • +1 more from TheKREATORS

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 166 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before claiming a change is unverifiable locally, check which case you are in:

    line 20
  2. Very specific:

    Always close the browser in a finally — a leaked Chromium process will hang the test run.

    line 53

“Common” is measured: kept by at least 6 in 10 of the 166 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

SituationWhat to do
The change touches a browser-testable surface in this repoVerify it locally with launchBrowser(). Do not defer to CI.
The executing environment genuinely lacks the capabilitySay so explicitly, name the missing capability, then fall back to CI.
The change is in another repo without this capabilityFall 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.

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.