ワンクリックで
quality-gate
Run all pre-commit quality checks in sequence: TypeScript, ruff, mypy, i18n coverage, static analysis, and security tests.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Run all pre-commit quality checks in sequence: TypeScript, ruff, mypy, i18n coverage, static analysis, and security tests.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | quality-gate |
| description | Run all pre-commit quality checks in sequence: TypeScript, ruff, mypy, i18n coverage, static analysis, and security tests. |
Runs the full openZero pre-commit check suite. Each step must pass before proceeding.
Run these commands in order. Stop and report on first failure:
TypeScript type check:
cd src/dashboard && npx tsc --noEmit
Python lint (ruff):
ruff check src/backend/
Python type check (mypy):
mypy src/backend/app/ --ignore-missing-imports
i18n key parity:
pytest tests/test_i18n_coverage.py -v
Static analysis:
pytest tests/test_static_analysis.py -v
Security tests:
pytest tests/test_security_prompt_injection.py -v
After all steps complete, provide a summary:
You can also run the bundled script directly:
bash .github/skills/quality-gate/scripts/run-quality-gate.sh
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).