Verify NewSystem changes

Run the correct verification gate for NewSystem based on changed scope: backend tests, frontend lint/test/build, or docs check. Required before declaring tasks complete.

Sby Skills Guide Bot
TestingIntermediate
308/30/2026
Claude CodeCursorWindsurfCopilotCodex
#verification#testing#backend#frontend#workflow

Recommended for


name: verify-newsystem description: Run the correct NewSystem verification gate for the scope that changed (backend tests in backend-node, or frontend lint/test/build in frontend-vue). Use before declaring a task complete, when asked to verify changes, or to confirm the testing gate from docs/AI-WORKFLOW.md §8.

Verify NewSystem changes

The test/verify commands are non-standard and split across two packages. Run only the gate(s) matching what actually changed; don't run frontend tests for a backend-only change.

Backend changed (backend-node/)

cd backend-node
npm test                # accounts + settings service tests
npm run test:iam-sdk    # IAM admin client tests
npm run test:contracts  # contract tests
# or, to run everything:
npm run test:all

Frontend changed (frontend-vue/)

cd frontend-vue
npm run lint
npm run test:unit
npm run test:e2e        # runs against a mock API
npm run build:prod
# or the bundled gate:
npm run verify          # lint + test:unit + test:e2e + build:prod

Docs-only change

No app test required. Verify links/paths by reading the changed docs and grep for stale references — unless a behavior/API/UI contract changed, in which case run the matching gate above.

Reporting (required by docs/AI-WORKFLOW.md §8)

State the exact commands run and their results. If a command could not run, report:

  • the command not run
  • the exact reason
  • the risk left open
  • the owner / next action

Do not declare the task done until the relevant gate passes or any failure is explicitly accounted for.

Related skills