verify-changes
Use this skill after implementing code to verify correctness before notifying the user.
When & Why to Use This Skill
The Verify Changes skill provides a robust QA protocol for AI agents to validate code integrity immediately after implementation. It automates essential verification steps—including type checking, backend testing, build validation, and UI smoke tests—ensuring that all modifications meet the 'definition of done' and maintain high software quality standards before user notification.
Use Cases
- Post-Implementation Verification: Automatically run type checks and unit tests after coding to ensure logic correctness and prevent regressions.
- UI/UX Integrity Checks: Execute specialized UI smoke tests after frontend modifications to verify that visual components and user interactions remain functional.
- Build and Runtime Validation: Perform full build cycles to catch bundler issues or environment-specific runtime errors before finalizing a task.
- Definition of Done Compliance: Use as a mandatory gatekeeper to ensure every code change adheres to project-specific quality benchmarks and linting rules.
| name | Verify Changes |
|---|---|
| description | Use this skill after implementing code to verify correctness before notifying the user. |
Verify Changes (QA Protocol)
Use this skill after code changes to meet the AGENTS.md “definition of done”.
When to use
- After any change that can affect build/runtime behavior.
- Always after UI/interaction changes (run UI smoke).
Standard checks (run from repo root)
Run these in order; if one fails, fix it before continuing:
- Typecheck + minimal lint
npm run check
- Backend tests (includes smoke)
npm test
- Build bundle (catches bundler/runtime issues)
npm run build
UI smoke (required when UI/interaction changed)
Pre-reqs:
- Build the frontend:
npm run build
- Start the backend serving
dist/on:4800:
npm run backend:start
Then run:
npm run test:ui:smoke
Notes
- If you only changed documentation, you can skip these commands.