kalpai：以 sklp 和 skt 管理由本地開發至正式環境的工作流程
kalpai's promise is simple: take a project from local dev to production and keep every signal — observability, CI, deploys — in
kalpai 以 sklp 和 skt 兩款命令列工具，將本地開發、CI/CD、部署及工具鏈管理整合於同一控制台。sklp 負責協調開發環境、CI/CD 流程、臨時環境、映像檔建置和部署，並支援以機器可讀格式供用戶及 AI Agent 使用。skt 是無需 root 權限的版本管理工具，透過 TOML 配方提供 15 款工具，並驗證下載檔案的 sha256 校驗碼。
kalpai's promise is simple: take a project from local dev to production and keep every signal — observability, CI, deploys — in one console. Under the hood, that console rests on two small command-line tools built with the same rule: nothing invented, everything assembled from what already works.
sklp — the developer CLI
sklp is the entry point. It orchestrates the local dev stack, runs CI/CD pipelines, manages ephemeral spaces, builds images and deploys — and watches the whole thing.
-
sklp dev/sklp run— local dev environment and pipelines from.sklp/YAML files -
sklp space— ephemeral, closed environments from.sklp/space.yaml -
sklp deploy/sklp image— pilot a node, build OCI images daemonless -
sklp logs,sklp issue,sklp flag— logs, issues and feature flags from the terminal -
sklp macosmanages the Linux VM it runs on under macOS (Virtualization.framework)
One command, machine-readable, built to be usable by both an operator and an AI agent.
skt — the rootless toolchain manager
Before any of that runs, you need the right binaries on the machine. That's skt: a standalone, rootless version manager. Give it <tool>@<version> and a target platform, and it returns the binary path as JSON.
skt resolve go@1.25.5 --json
skt install go@1.25.5 --json
It replaces the mise fallback we used in sklp. Four steps, nothing more:
- Resolve — map
<tool>@<version>to a release for the host OS/arch - Download — fetch the artifact from the recipe's URL
- Verify — stream a sha256, compare constant-time to the published checksum
- Cache — extract into
$XDG_CACHE_HOME/skt; warm hits skip the network
Recipes, not code
Every supported tool is a declarative TOML recipe — 15 bundled (air, bun, dive, gdu, gitleaks, golangci-lint, helm, jq, just, kubectl, nuclei, opentofu, task, trivy, wasm-bindgen). Each declares per-platform artifacts and a checksum strategy. Adding a tool is adding a recipe, not writing fetching logic.
Why it holds
Rootless, cached, verified, machine-readable. The toolchain manager thinks the way a CI system does: deterministic resolution, checksum-checked downloads, content cache. sklp orchestrates the what-to-run, skt the with-what.
What's next
The cache is the last step before the release.
來源：DEV Community · dev.to