Verifying Changes
When this applies
Before telling the user a fix, feature, or bug is done, choose the smallest
proof that exercises the behavior you changed and use the row below as a guide.
"I changed the code and it looks right" is not proof — it's the exact gap this
skill exists to close. A failing check is a reason to keep working, not a reason
to stop, ask, or report done anyway.
Scale the verification
Verification proves the changed behavior; it is not a reason to run a broad
workspace audit after every edit.
- For a localized one-line or small-file change, inspect the diff and run the
narrowest relevant test, typecheck, formatter, or direct invocation. Do not
run
pnpm run prep, browser automation, or restart a dev server unless the
changed area requires it.
- For an action or capability-card change, use the focused action/card check.
Restart only when the runtime process must reload registration or the change
explicitly affects startup.
- Escalate to package-wide tests or
pnpm run prep for shared contracts,
cross-cutting changes, migrations, or when a focused check exposes a wider
failure. Keep repository-required guards and doctor checks when they apply.
- If a focused check is unavailable, state the exact gap rather than replacing
it with unrelated expensive work.
Do NOT report done in these situations
- The change is "obviously correct" or one line — obvious fixes are the ones
that ship broken most often; run the smallest relevant proof anyway.
- You verified a similar path earlier in the session — re-run against the
actual latest edit, not a memory of an earlier pass.
- The user didn't explicitly ask you to test it — test it anyway; verify-
before-done is a standing rule here, not an opt-in.
- The full test suite is slow or flaky — run the targeted command for the
changed area (below) instead of skipping verification entirely.
- You're mid-task and unsure whether to keep going — keep going. Only stop for
a missing credential, an ambiguous decision only the user can make, or a
destructive action that needs confirmation. Silence from the user means
keep working, not pause and wait.
- You genuinely cannot run anything — say so out loud (see below); never let
"unverified" read as "done".
Proof by area
| You changed |
What proves it |
Command |
Template UI/behavior (templates/<app>/app/**) |
Drive the real page and check console + network, not just the diff |
pnpm --filter <app> dev (or root pnpm dev for the gateway), then click through the exact flow with whatever browser tool is available; check for console errors and failed (4xx/5xx) requests on that page. A sign-in screen is not a blocker: POST /_agent-native/auth/local-dev from the page's own context (Playwright page.request.post) signs in as the local dev account |
An action (templates/<app>/actions/*.ts) |
Call it with representative args and inspect the real return value |
cd templates/<app> && pnpm action <name> --key value; for a write, follow with pnpm action db-query --sql "SELECT ..." to confirm the row actually landed |
| Schema/migration |
Boot the app so migrations run, then read back the new column/table |
pnpm --filter <app> dev once, then cd templates/<app> && pnpm action db-query --sql "..." (action is a per-template script, not a root one); pnpm guard:additive-migrations catches destructive DDL before CI does. For a core store: pnpm gen:store-registry, then pnpm guard:release-schema-complete |
A guard/lint script (scripts/guard-*.{mjs,ts}) |
Run it directly against a case that should now pass and one that should still fail |
pnpm guard:<name> (name matches the package.json script); pnpm guards for the full sweep |
packages/core or another publishable package |
Run that package's actual tests, not just typecheck |
pnpm --filter @agent-native/core exec vitest --run <changed.spec.ts>, or pnpm test:core-integration for cross-cutting paths |
A CI job, workflow, or scripts/ci-*.ts |
Show the new scope on real history; the PR's own CI is a full run and cannot show it |
node --experimental-strip-types --test scripts/ci-change-scope.test.ts, then run scripts/ci-change-scope.ts with GITHUB_OUTPUT on real main commits; see adding-tests-and-ci |
A deploy guide (node-js.mdx, docker.mdx, netlify.mdx, vercel.mdx) or a package a standalone Chat app installs |
Run the documented path: scaffold, migrate a real Postgres, build, run, sign up, restart |
pnpm qa:deploy-paths --target node, docker (Docker required; it starts its own Postgres), or presets (the Netlify and Vercel build output). --target netlify or vercel deploys to a real an-deploy-ci-<host>-<slot> project, created once and reused, and needs DEPLOY_CHECK_DATABASE_URL plus that host's login (--netlify-account-slug, --vercel-scope). --source npm proves what is published instead of this checkout |
| Cross-cutting change, or unsure which area |
Workspace-wide pass |
pnpm run prep (fmt + typecheck + test:fast + guards, run in parallel) |
| Deployed behavior (when requested or environment-specific) |
Add a deployed check only when requested or a concrete beta/production difference could make local proof misleading (for example, deploy-time config or secrets, host/cookie/OAuth settings, CDN/SSR, serverless runtime, storage, or external connectivity). A merge-triggered deploy alone is not a reason to retest every path remotely; focused local proof and required CI are the default. When warranted, exercise the affected path on that environment and inspect relevant logs; deploy success alone is not behavior proof |
|
Docs only (.md, AGENTS.md, SKILL.md) |
Nothing to run |
Say "docs-only, no runtime check applies" — don't invent a verification step |
For any user-visible change, put the proof in the reply: a screenshot of the
surface you just drove, or the actual query result / log line for backend work.
"Show me screenshots" is a standing expectation, not a special request.
pnpm test:fast excludes .db.test.ts / .integration.* / .e2e.* /
.live.* / .perf.* suites. If your change touches one of those, name and
run that specific file — test:fast passing does not cover it.
Production forensics
When inspecting production runs, query interactive and scheduled/background
work as separate populations before summarizing reliability. Report both
id NOT LIKE 'job-%' and id LIKE 'job-%' (or the repo's current equivalent),
including app, run count, completed count, failure count, and top terminal
reasons for each slice. A healthy interactive sample does not prove scheduled
jobs work.
When you can't verify
State it plainly and name what would close the gap: "I could not run this —
verifying it needs <command> or a browser check of <page>." Never write
"should be fixed" or "this resolves it" without having actually run the check
above.
Real failures this replaces
- "still getting it friend. this is the third time you said you fixed it when
you didn't. please reproduce end to end and verify"
- "did you test end to end? can you do so in the browser and confirm?" — asked
on nearly every wrap-up before this rule existed
- "ok so should work now?? i am getting sick of saying 'try this' and it still
not working. you confident?"
- "my analytics dashboards ALWAYS fail ... i have asked agents to fix this for
weeks at least 10x and they always say they did and then the emails keep
failing"
- "WHY THE FUCK DO YOU KEEP STOPPING" / "sorry what is still queued? you
should be doing everything now don't queue" — stopping mid-task instead of
finishing and verifying
1---2name: verifying-changes3description: >-4 Concrete, per-area proof that a change actually works before reporting it5 fixed, done, or "should work now" — which dev server, test command, or6 invocation proves a template UI change, an action, a migration, a guard, or7 a core/package change. Use before every wrap-up, and before stopping8 mid-task to ask permission instead of continuing.9scope: dev10metadata:11 source: https://skillmd.com/skills/builderio/verifying-changes12 internal: true13---1415# Verifying Changes1617## When this applies1819Before telling the user a fix, feature, or bug is done, choose the smallest20proof that exercises the behavior you changed and use the row below as a guide.21"I changed the code and it looks right" is not proof — it's the exact gap this22skill exists to close. A failing check is a reason to keep working, not a reason23to stop, ask, or report done anyway.2425## Scale the verification2627Verification proves the changed behavior; it is not a reason to run a broad28workspace audit after every edit.2930- For a localized one-line or small-file change, inspect the diff and run the31 narrowest relevant test, typecheck, formatter, or direct invocation. Do not32 run `pnpm run prep`, browser automation, or restart a dev server unless the33 changed area requires it.34- For an action or capability-card change, use the focused action/card check.35 Restart only when the runtime process must reload registration or the change36 explicitly affects startup.37- Escalate to package-wide tests or `pnpm run prep` for shared contracts,38 cross-cutting changes, migrations, or when a focused check exposes a wider39 failure. Keep repository-required guards and doctor checks when they apply.40- If a focused check is unavailable, state the exact gap rather than replacing41 it with unrelated expensive work.4243## Do NOT report done in these situations4445- The change is "obviously correct" or one line — obvious fixes are the ones46 that ship broken most often; run the smallest relevant proof anyway.47- You verified a similar path earlier in the session — re-run against the48 actual latest edit, not a memory of an earlier pass.49- The user didn't explicitly ask you to test it — test it anyway; verify-50 before-done is a standing rule here, not an opt-in.51- The full test suite is slow or flaky — run the targeted command for the52 changed area (below) instead of skipping verification entirely.53- You're mid-task and unsure whether to keep going — keep going. Only stop for54 a missing credential, an ambiguous decision only the user can make, or a55 destructive action that needs confirmation. Silence from the user means56 keep working, not pause and wait.57- You genuinely cannot run anything — say so out loud (see below); never let58 "unverified" read as "done".5960## Proof by area6162| You changed | What proves it | Command |63| --- | --- | --- |64| Template UI/behavior (`templates/<app>/app/**`) | Drive the real page and check console + network, not just the diff | `pnpm --filter <app> dev` (or root `pnpm dev` for the gateway), then click through the exact flow with whatever browser tool is available; check for console errors and failed (4xx/5xx) requests on that page. A sign-in screen is not a blocker: `POST /_agent-native/auth/local-dev` from the page's own context (Playwright `page.request.post`) signs in as the local dev account |65| An action (`templates/<app>/actions/*.ts`) | Call it with representative args and inspect the real return value | `cd templates/<app> && pnpm action <name> --key value`; for a write, follow with `pnpm action db-query --sql "SELECT ..."` to confirm the row actually landed |66| Schema/migration | Boot the app so migrations run, then read back the new column/table | `pnpm --filter <app> dev` once, then `cd templates/<app> && pnpm action db-query --sql "..."` (`action` is a per-template script, not a root one); `pnpm guard:additive-migrations` catches destructive DDL before CI does. For a core store: `pnpm gen:store-registry`, then `pnpm guard:release-schema-complete` |67| A guard/lint script (`scripts/guard-*.{mjs,ts}`) | Run it directly against a case that should now pass and one that should still fail | `pnpm guard:<name>` (name matches the `package.json` script); `pnpm guards` for the full sweep |68| `packages/core` or another publishable package | Run that package's actual tests, not just typecheck | `pnpm --filter @agent-native/core exec vitest --run <changed.spec.ts>`, or `pnpm test:core-integration` for cross-cutting paths |69| A CI job, workflow, or `scripts/ci-*.ts` | Show the new scope on real history; the PR's own CI is a full run and cannot show it | `node --experimental-strip-types --test scripts/ci-change-scope.test.ts`, then run `scripts/ci-change-scope.ts` with `GITHUB_OUTPUT` on real `main` commits; see `adding-tests-and-ci` |70| A deploy guide (`node-js.mdx`, `docker.mdx`, `netlify.mdx`, `vercel.mdx`) or a package a standalone Chat app installs | Run the documented path: scaffold, migrate a real Postgres, build, run, sign up, restart | `pnpm qa:deploy-paths --target node`, `docker` (Docker required; it starts its own Postgres), or `presets` (the Netlify and Vercel build output). `--target netlify` or `vercel` deploys to a real `an-deploy-ci-<host>-<slot>` project, created once and reused, and needs `DEPLOY_CHECK_DATABASE_URL` plus that host's login (`--netlify-account-slug`, `--vercel-scope`). `--source npm` proves what is published instead of this checkout |71| Cross-cutting change, or unsure which area | Workspace-wide pass | `pnpm run prep` (fmt + typecheck + `test:fast` + `guards`, run in parallel) |72| Deployed behavior (when requested or environment-specific) | Add a deployed check only when requested or a concrete beta/production difference could make local proof misleading (for example, deploy-time config or secrets, host/cookie/OAuth settings, CDN/SSR, serverless runtime, storage, or external connectivity). A merge-triggered deploy alone is not a reason to retest every path remotely; focused local proof and required CI are the default. When warranted, exercise the affected path on that environment and inspect relevant logs; deploy success alone is not behavior proof |73| Docs only (`.md`, `AGENTS.md`, `SKILL.md`) | Nothing to run | Say "docs-only, no runtime check applies" — don't invent a verification step |7475For any user-visible change, put the proof in the reply: a screenshot of the76surface you just drove, or the actual query result / log line for backend work.77"Show me screenshots" is a standing expectation, not a special request.7879`pnpm test:fast` excludes `.db.test.ts` / `.integration.*` / `.e2e.*` /80`.live.*` / `.perf.*` suites. If your change touches one of those, name and81run that specific file — `test:fast` passing does not cover it.8283## Production forensics8485When inspecting production runs, query interactive and scheduled/background86work as separate populations before summarizing reliability. Report both87`id NOT LIKE 'job-%'` and `id LIKE 'job-%'` (or the repo's current equivalent),88including app, run count, completed count, failure count, and top terminal89reasons for each slice. A healthy interactive sample does not prove scheduled90jobs work.9192## When you can't verify9394State it plainly and name what would close the gap: "I could not run this —95verifying it needs `<command>` or a browser check of `<page>`." Never write96"should be fixed" or "this resolves it" without having actually run the check97above.9899## Real failures this replaces100101- "still getting it friend. this is the third time you said you fixed it when102 you didn't. please reproduce end to end and verify"103- "did you test end to end? can you do so in the browser and confirm?" — asked104 on nearly every wrap-up before this rule existed105- "ok so should work now?? i am getting sick of saying 'try this' and it still106 not working. you confident?"107- "my analytics dashboards ALWAYS fail ... i have asked agents to fix this for108 weeks at least 10x and they always say they did and then the emails keep109 failing"110- "WHY THE FUCK DO YOU KEEP STOPPING" / "sorry what is still queued? you111 should be doing everything now don't queue" — stopping mid-task instead of112 finishing and verifying