Menu
Run validation checks - determines whether to use fast (validate) or full (validate:full) based on changed files
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Create a pull request with a concise, useful description
Security code review for vulnerabilities. Use when asked to "security review", "find vulnerabilities", "check for security issues", "audit security", "OWASP review", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting.
Create and manage isolated Docker workspaces on your tailnet with Claude Code and OpenCode pre-installed. Use when working with Perry workspaces, connecting to coding agents, or managing remote development environments.
React and Next.js performance optimization guidelines from Vercel Engineering. Contains 45+ rules across 8 categories.
Cut a new release - bump version, commit, tag, and push to trigger CI publish
| name | validate |
| description | Run validation checks - determines whether to use fast (validate) or full (validate:full) based on changed files |
Run the appropriate validation for your changes.
| Command | What it does | When to use |
|---|---|---|
bun run check | lint + format + typecheck | Quick syntax check |
bun run validate | check + build TS/worker + unit tests | Default for most changes |
bun run validate:core | validate + integration tests | Core behavior changes |
Check what files changed using git status or git diff --name-only
Use bun run validate:core if changes touch:
src/agent/ (core agent behavior)src/workspace/ (workspace lifecycle)src/terminal/ (terminal/WebSocket)Use bun run validate for everything else
Run specific tests relevant to your changes instead of full suites:
bun test test/unit/relevant.test.ts
bun test test/integration/relevant.test.ts
bun test web/e2e/relevant.spec.ts
Check changed files:
git diff --name-only HEAD
Run validation + relevant tests:
bun run validate
# Then run specific tests for your changes
bun test test/unit/relevant.test.ts
If validation fails, fix issues and re-run
Run warden to get code review feedback locally (security, react best practices, code simplification):
warden -v
The -v flag streams findings in real-time. Fix any issues warden finds before creating a PR.
validate is fast (~30s), validate:core adds integration tests (~1-2min)