# Verify > Verify Check CX changes by running the right local checks and manually exercising UI behavior when relevant. Use when this capability is needed. - Skill: `tomevault-io/verify-9` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/verify-9` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/verify-9/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/verify-9 --- Use this skill when validating local changes before reporting them complete. 1. Run `pnpm lint` for any code change. 2. Run `pnpm build` when changes touch routing, server code, dependencies, config, Docker/deployment behavior, or anything that can affect production output. 3. For UI or frontend behavior changes, start the app with `pnpm dev`, open the affected route in a browser, exercise the golden path and obvious edge cases, and check the page for visual regressions. 4. If Supabase schema, migrations, or provider configuration behavior changed, state which migration/config path was checked and whether a staging database replay is still needed. 5. If a check cannot be run because credentials or environment are missing, say exactly what is missing instead of claiming verification succeeded. --- > Source: [BingZi-233/check-cx](https://github.com/BingZi-233/check-cx) — distributed by [TomeVault](https://tomevault.io).