Validation

Use the smallest command that matches the surface you changed. That keeps feedback fast while still protecting the public docs, generated workspace shape, and MCP context path.

Core Checks

npm ci
make check
npm run docs:build

make check confirms the core repository files exist and type-checks the MCP server through npm run mcp:check.

MCP Checks

npm run mcp:check
npm run mcp:test
npm run mcp:smoke

Run these after changing mcp/, repo registry loading, resource names, search behavior, or package scripts that affect MCP startup.

Generator Checks

npm run test:create-index
node generator/create-index.mjs --help

Run these after changing generator/create-index.mjs, profiles, templates, CLI flags, or generation defaults.

Generated repositories also include npm run validate, which checks baseline files, section schemas for projects/, partners/, and connectors/, required Markdown frontmatter, notification config, and notification template references.

Workspace Metadata Checks

npm run validate:workspaces
npm run test:workspaces

Run these after changing workspace records, people records, schemas, validation rules, enums, dates, references, or suspicious secret-like key checks.

Docs Checks

npm run docs:build
npm run docs:preview

The docs build should emit the VitePress site and LLM-friendly output. Preview the built site when changing navigation, sidebar structure, theme styles, or public copy.