---

name: validate description: Run validation checks - determines whether to use fast (validate) or full (validate:full) based on changed files

Validate Skill

Run the appropriate validation for your changes.

Commands

Decision Logic

1. Check what files changed using git status or git diff --name-only

2. Use bun run validate:core if changes touch:

   • src/agent/ (core agent behavior)
   • src/workspace/ (workspace lifecycle)
   • src/terminal/ (terminal/WebSocket)

3. Use bun run validate for everything else

4. Run specific tests relevant to your changes instead of full suites:

   Copybun test test/unit/relevant.test.ts
   bun test test/integration/relevant.test.ts
   bun test web/e2e/relevant.spec.ts
   

Steps

1. Check changed files:

   Copygit diff --name-only HEAD
   

2. Run validation + relevant tests:

   Copybun run validate
   # Then run specific tests for your changes
   bun test test/unit/relevant.test.ts
   

3. If validation fails, fix issues and re-run

Run Review Agents in Parallel

While validation runs, spawn review subagents in parallel based on what changed:

These agents review your local changes and report issues. Run them in parallel with validation to save time.

Notes

• validate is fast (~30s), validate:core adds integration tests (~1-2min)
• CI runs full validation on PRs, so targeted tests are usually sufficient locally