用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/zenml-io/kitaru --skill kitaru-dev命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Full reference for Kitaru v2 development commands, tests, docs generation, packaging, Docker builds, and CI workflows. Use when a task needs commands beyond just check, just fix, or just test.
Prepare or execute Kitaru core and plugin releases, including Kitaru UI publication in the frontend monorepo, version and changelog updates, frontend declarations, default plugin pins, validation, release tags, artifact verification, and recovery. Use when a user asks to prepare, cut, publish, verify, or recover a Kitaru, Kitaru UI, or Kitaru plugin release.
Use for Kitaru tests, CI, releases.
基于 SOC 职业分类
正在显示 SKILL.md
| name | kitaru-dev |
| description | Use for Kitaru commands, CLI, analytics, PRs. |
Use this when you need the command catalog beyond the daily loop in the root AGENTS.md, or when adding CLI commands, analytics events, or PR descriptions.
uv sync: install the base SDK and development dependenciesuv sync --extra cli: include the optional CLIuv sync --extra mcp: include the optional native MCP serveruv sync --extra server: include server componentsuv sync --extra worker: include worker componentsuv sync --extra otel: include OpenTelemetry integrationsjust check: run formatting, lint, OpenAPI freshness, typecheck, typos, YAML, actions lint, and linksjust openapi-check: verify that the committed OpenAPI specification matches the application schemajust fix: auto-fix formatting, lint issues, and YAMLjust test: run the full pytest suitejust test tests/test_file.py::test_name: run one targeted testjust lint: lint onlyjust typecheck: type check onlyjust typos: typo check onlyjust format-check: check formatting without modifying filesjust yaml-check: check YAML formattingjust actions-lint: lint GitHub Actions workflows; requires actionlintjust zizmor: audit GitHub Actions workflow security with zizmorjust audit: audit Python dependencies with pip-audit and the documented ignore listjust links: check Markdown links offline; requires lycheejust links-external: check links including external URLs; slowjust example-coverage-audit: validate examples/example-coverage.yaml metadata and waiversjust build: build wheel and sdist locallyjust cli-artifact-smoke: verify clean CLI wheel and source installationsjust plugin-artifact-smoke: build every default-plugin wheel, load its configured entrypoints, and verify default registrationjust mcp-schema-check: verify public MCP registry budgets and committed snapshotsjust mcp-wheel-smoke: verify clean base and [mcp] installs from the wheel under dist/just migration-check: compare Alembic migrations with the ORM schema; requires PostgreSQLThere is no v2 kitaru init command or local extra. Do not carry the v1 .kitaru/ project-marker setup into v2 instructions or tests.
When merging the v2 base into a feature branch and resolving pyproject.toml or uv.lock, check recent dependency-security changes before regenerating the lockfile broadly. Use targeted upgrades when a package was intentionally bumped and run just audit before pushing.
These require Node 22+ and pnpm.
just docs: preview docs locally at localhost:3000just docs-build: build the static docs exportjust docs-validate: validate the export as served under /docsThe v2 checkout currently lacks scripts/generate_sdk_docs.py, so just generate-docs and the SDK-reference generation step in docs CI are blocked. Do not advertise them as healthy or restore the deleted v1 generator without reviewing the v2 public SDK surface. CLI contracts remain available offline through kitaru schema; CLI reference publishing is deferred.
The native v2 server is installed with kitaru[mcp] and started with kitaru-mcp. It defaults to read-only; standard and destructive expose progressively broader capabilities.
Treat tests/mcp/snapshots/metrics.json and src/kitaru/mcp/registry.py as the inventory authorities. Do not copy tool counts into prose. Run just mcp-schema-check after changing MCP models, registry declarations, descriptions, annotations, or SDK versions. Build the wheel and run just mcp-wheel-smoke after entrypoint, packaging, lifecycle, or optional-import changes.
The kitaru console script is defined in pyproject.toml under [project.scripts]. src/kitaru/cli/__init__.py is the lazy entry point, src/kitaru/cli/app.py registers the shared Cyclopts applications, and command implementations live under src/kitaru/cli/.
Register new leaf commands through the _spec(...) and _register(...) metadata in src/kitaru/cli/app.py. Tests should call main([...]) with an explicit argument list and assert the returned integer exit code.
Agent-facing commands use the version-1 structured contract. Success documents include schema_version, command, ok, warnings, links, and next_actions, plus item for one result or items, count, and page for a list. Streaming commands emit JSONL events. Structured errors are one JSON object on stderr with a stable error kind and exit code.
For agent-facing use, prefer --output json --machine --non-interactive --no-browser. A deliberate dashboard or device-login handoff is the exception.
Document login consistently: kitaru login SERVER targets the full managed or self-hosted instance URL, while kitaru login --local provisions or reuses the CLI-owned Docker Compose deployment at http://localhost:8000. kitaru logout stops that deployment when it is selected, and kitaru logout --volumes also deletes its PostgreSQL data.
kitaru status shows the selected server, provenance, credential state, compatibility, and live-worker count. kitaru info adds local package, Python, platform, and server details. kitaru doctor runs independent local, server, authentication, and tooling checks without stopping after the first failure. These commands never print secret values.
Analytics events live in src/kitaru/analytics/events.py; source attribution lives in src/kitaru/analytics/source.py. Server-side feature events are emitted through the application analytics service. MCP attribution is set once for the MCP lifecycle through AnalyticsSource.MCP.
AnalyticsEvent in src/kitaru/analytics/events.py.Use a clear human-readable title without a [Codex] prefix. Include what changed, why it was needed, important implementation decisions, and reviewer focus areas. Link related issues when applicable.
Every PR description should include a Reviewer Notes H2 or H3 section that explains the story and risks of the change, plus a concrete Reproduction subsection. Keep local hygiene commands as a short note after reproduction rather than using them as a substitute for reviewer guidance.