Skip to content
Back to skills

Verify

ASecurity

Check previews or CI behavior, report results and remaining help; also tests APIs or screenshots.

  • 6 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 27, 2026
ai-agentsbashnodegitapi

Works with

  • cli
  • api

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned October 5, 2026

npx -y skills add matthewwong525/WongStack --skill verify --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Verify?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Verify
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/matthewwong525-verify/badge)](https://www.skillsdirectory.com/skills/matthewwong525-verify)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: verify
description: Check previews or CI behavior, report results and remaining help; also tests APIs or screenshots.
user-invocable: true
---

# /verify

Check fresh scenarios on the exact saved revision. [Reference](references/walkthrough.md): how; [wiki](../../../wiki/development/staging-walkthrough.md): why. Gates nothing.

Authorized: needed `/save` (kept checks' too), browser installation, Access heal, staging preparation and § a's writes; other permissions join the handoff.

## Order

```bash
ROOT="$(git rev-parse --show-toplevel)"
bash "$ROOT/.claude/skills/verify/scripts/verify-staging.sh" scout-check
bash "$ROOT/.claude/skills/verify/scripts/verify-staging.sh" preflight
```

1. **Scout.** [Rungs](../save/references/checkpoint-evidence.md#selection-rungs): `explicit` (including `/ship`'s archive), `session`, `changed-active`, `recorded-branch`, `changed-archive`. Asks name candidates' scenarios. READY → match probes/recipes/consumers by [§ a](references/walkthrough.md#a--scout-the-scenarios); nothing reachable → NONE, name exclusions and stop.
2. **Bind.** Run `node "$ROOT/.claude/skills/save/scripts/saved-revision.mjs"` with the caller's `--checkpoint <file>`. NEEDS_SAVE → `/save`; SAVED → reuse its matching receipt or read the existing [gate](../save/references/git-gate.md#saved-revision-handoff). UNKNOWN → unverified, never save speculatively. No record edits or settled-check reruns. **Prepare independently.** Then `preflight` (allow 12 minutes for the staging turn); no browser journeys → `--no-browser`. `SEEDED=no` beside a `TURN` line → staging-data checks unverified, with its reason; report `TURN=unavailable`. CI-only/missing preview → `--no-preview --no-browser`, then [collect](references/ci-evidence.md). Blocks pause dependents; never guess URLs. Recheck head before posting; changes require fresh evidence.
3. **Walk/grade** by [§§ b–f](references/walkthrough.md#b--write-the-journeys); finish independent safe checks before repairs. Inside `/ship`, add [kept checks](references/walkthrough.md#g--kept-checks).
4. **FAILURE** → [judge scope](references/walkthrough.md#e--after-a-failure). In scope → collect failures, fix once, `/save`, `preflight`, repeat affected checks **at most twice**; retain independent evidence only with unchanged dependencies; otherwise report.
5. **Simulate/report** by [§ f](references/walkthrough.md#f--post-the-evidence-then-clean-up); one report covers surfaces/retries, heals/fixes/installs and scope/limits. [Next step](../explore/references/asking-the-user.md#end-every-reply-with-the-next-step); inside `/ship`, return the verdict.

## When a block stops the walk

Heal **once per invocation**; retry dependents only.

**BLOCK=access-challenge (exit 3)**: with a Cloudflare API token, mint a repo-named service token; widen groups if needed. Confirm the owned app's machine policy accepts it; preserve human permissions. Store the pair in **primary worktree** `.env` only ([secrets](../../../wiki/development/secrets.md), [Access](../../../wiki/stack/cloudflare-access.md), [authorized widen](../../../wiki/stack/cloudflare-credentials.md#the-widen-is-pre-authorized)). Name the mint; never print/commit credentials. Privacy changes need human login/revocation checks; machine access proves no email login.

No token/surviving block → unverified; name credentials/repair gaps.

## Plain checks

Named screenshot/request/click-through: skip scout, use its address and `mktemp -d "${TMPDIR:-/tmp}/wong-verify-XXXXXX"`; otherwise bind/preflight. Same safeguards/handoff. Past pictures: `verify-staging.sh pictures <pr>`. Show evidence; post only if asked; `cleanup`.

## Verdicts

| Verdict | Meaning | Report |
|---|---|---|
| **NONE** | no scenario reachable | what was there instead |
| **SUCCESS** | no contradiction or blocked reachable check | evidence, including each [partly shown](references/walkthrough.md#d--grade-against-the-written-expectation) claim |
| **FAILURE** | evidence contradicts a `THEN` | evidence, fix only in scope |
| **UNKNOWN** | reachable check blocked or ambiguous | unverified, why and needed help |
| **TIMEOUT** | budget exceeded | unverified, what completed and where it stopped |

Precedence: FAILURE, TIMEOUT, UNKNOWN. [`UNKNOWN` is not `NONE`](../save/references/git-gate.md#2--wait-for-checks-auto-fix-on-failure) ([why](../../../wiki/development/staging-walkthrough.md#the-verdicts)).

## Hard rules

- [`agent-browser`](../agent-browser/SKILL.md)/Chrome only for browser journeys. New probe runtimes ask first; bundled collector authorized. No repo dependencies.
- Saved-source previews/validated CI captures; [no local repo execution/invented tooling](../../../wiki/development/staging-walkthrough.md#what-it-is-not). Read-only recipes; written expectations judge.
- Keep journeys/evidence outside the repo, bar `/ship`'s kept checks; `cleanup` on **every** exit, including UNKNOWN/handoff.
- Never merge/archive: `/ship` owns that.

Files in this skill

  • SKILL.md7.3 KB
  • references/walkthrough.md13 KB
  • scripts/verify-runner.sh8.1 KB
  • scripts/verify-staging.sh15.4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.