Menu
Run the full openZero deploy pipeline: build dashboard, commit, push, sync to VPS, and optionally run live regression tests.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | deploy-vps |
| description | Run the full openZero deploy pipeline: build dashboard, commit, push, sync to VPS, and optionally run live regression tests. |
Deploys the current state of the openZero repository to the production VPS.
Build dashboard:
cd src/dashboard && npm run build
Stage and commit (if there are uncommitted changes):
git add -A && git status
Ask the user for a one-line commit message. Commit:
git commit -m "<user message>"
Push to remote:
git push
Sync to VPS:
bash scripts/sync.sh
Optional: Live regression test (if user requested --test):
pytest tests/test_live_regression.py -v
docker compose ps on VPS.docker compose logs --tail=20 backend.Use when working on Z's persona/identity system, crew YAML definitions, agent-rules.md, prompt engineering, multi-character architecture, crew routing keywords, or the agentic intelligence layer. Expert in Semantic Priming and LLM behaviour shaping.
Use when working on FastAPI endpoints, Python services, scheduled tasks, LLM routing, message bus, memory, voice/TTS, notifier, email rules, or any external API wrapper (Calendar, Gmail, SearXNG, Qdrant, weather). Covers the entire src/backend/ codebase.
Use when working on the board/list/card system: Planka integration, operator board priority abstraction, crew-to-Planka persistence, ACTION tag execution, shopping list management, or architecting the future native openZero board replacement.
Use when working on commercialisation strategy: BSL-1.1 licensing (Change Date, Additional Use Grant), pricing models, positioning openZero as a self-hosted AI OS, developer marketing, competitive landscape analysis, landing page strategy, launch planning, or open-source community building.
Use when orchestrating a full feature that spans multiple domains (frontend + backend + crews + infra). Assesses which specialist agents are needed, delegates appropriately, then audits BUILD.md and artifacts for staleness. User-invocable orchestrator.
Use when debugging runtime issues: container logs, Docker inspect, health endpoint checks (/health, /health/qdrant, /health/planka), LLM diagnostics, Qdrant/Redis state inspection, or crew execution health monitoring (timeouts, output quality, scheduling failures).