Menú
Use when configuring, debugging, or modifying CNB (Cloud Native Build) CI/CD pipelines for VoltUI/西谷智灯暗涌系统. Covers .cnb.yml structure, auto-release conventional commit workflow, merge-request CI checks, cross-repo PR creation, and CNB Release API.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | cnb-ci-cd |
| description | Use when configuring, debugging, or modifying CNB (Cloud Native Build) CI/CD pipelines for VoltUI/西谷智灯暗涌系统. Covers .cnb.yml structure, auto-release conventional commit workflow, merge-request CI checks, cross-repo PR creation, and CNB Release API. |
This skill covers the CNB (cnb.cool) CI/CD system used for the 西谷智灯暗涌系统 fork of VoltUI.
| Component | Responsibility | Trigger |
|---|---|---|
CNB CI (.cnb.yml) | Version calculation + Windows desktop build + minisign + CNB Release assets | feat:/fix: commit to main |
GitHub Actions (release.yml) | Legacy upstream CLI/npm release path | v* tag push |
Current CNB desktop scope: CNB Linux Docker runners cross-compile Windows amd64 Wails artifacts and use Linux nsis/makensis to produce the installer. macOS and Linux desktop artifacts are intentionally disabled until their CNB build strategy is confirmed.
main:
push:
- docker:
image: golang:1.26
stages:
- name: build
script: make build
- name: test
script: go test ./...
SemVer logic:
feat!: or fix!: → major bump (desktop-v{X+1}.0.0)feat: → minor bump (desktop-v{X}.{Y+1}.0)fix: → patch bump (desktop-v{X}.{Y}.{Z+1})[skip-release] → skip entirelyThe auto-release pipeline:
desktop-v* tagnsiswindows/amd64, builds the NSIS installer, signs artifacts, and generates latest.jsondesktop-v* tagmerge-request:
- docker:
image: golang:1.26
stages:
- name: build-check
script: make build
- name: test
script: go test ./...
Syncs from upstream aizhuliren/volt-gui via scripts/sync-upstream.sh, then creates PR via CNB API.
POST ${CNB_API_ENDPOINT}/${CNB_REPO_SLUG}/-/releases
Headers: Authorization: Bearer ${CNB_TOKEN}, Content-Type: application/json
Body: { tag_name, name, body, draft, prerelease }
POST .../asset-upload-url → get upload_url + verify_urlPUT upload_url → upload file binaryPOST .../asset-upload-confirmation/{token}/{path}?ttl=0 → confirmPOST https://api.cnb.cool/{upstream-slug}/-/pulls
Body: { title, body, head, base }
For cross-repo: push branch to upstream first, then create PR.
| Tag pattern | What it triggers | Example |
|---|---|---|
desktop-v* | CNB desktop release record and artifact upload | desktop-v1.6.0 |
v* | Legacy upstream GitHub release.yml (CLI/npm) | v1.6.0 |
Never mix namespaces — desktop releases use desktop-v*, CLI releases use v*.
| Variable | Source | Usage |
|---|---|---|
CNB_COMMIT_MESSAGE | CNB CI runtime | Conventional commit detection |
CNB_REPO_SLUG | CNB CI runtime | API calls |
CNB_TOKEN | CNB CI runtime | API authentication |
CNB_API_ENDPOINT | CNB CI runtime | API base URL (default: https://api.cnb.cool) |
MINISIGN_PRIVATE_KEY | CNB secret | Desktop artifact signing key |
MINISIGN_PASSWORD | CNB secret | Desktop artifact signing password |
| `XIGU_BRAND_NAME: "西谷智灯暗涌系统") | ||
VOLTUI_BRAND_NAME | Runtime | Desktop build artifact naming |
| Problem | Cause | Fix |
|---|---|---|
| Release created but no artifacts | CNB asset upload failed after release creation | Check publish-cnb-release logs and CNB_TOKEN permissions |
| Signing fails | Missing minisign secrets | Configure MINISIGN_PRIVATE_KEY and MINISIGN_PASSWORD in CNB |
| macOS/Linux artifacts missing | They are intentionally disabled in .cnb.yml | Enable them only after confirming the CNB build strategy |
| Cross-repo PR fails: branch not found | Branch not pushed to upstream repo | git push upstream <branch> first |
| Build/test stage fails | Go version mismatch | Update docker image to golang:1.26 |
Define, implement, and review the Volt GUI desktop design language and user experience. Use for any Volt GUI Svelte/Wails UI work involving visual styling, layout, navigation, Work/Code workbenches, composer interactions, settings, dialogs, lists, empty/loading/error states, responsive behavior, or design-system decisions.
Use when designing, implementing, or reviewing Volt GUI operational task-lifecycle UX: running message queues and Steer, activity centers, result receipts, structured recovery, explainable approvals, Diff comments to fixes, automation result inboxes, or managed worktree snapshot/Handoff flows. Enforces real Wails-backed state, safe mutation preflights, Work/Code ownership, and behavioral plus visual verification; pair with the project volt-gui-design-language skill for broad visual or layout work.
Use when configuring, verifying, or debugging the 西谷智灯暗涌系统 (Anyong/Xigu AI) white-label branding on the VoltUI fork. Covers BrandConfig env vars, voltui.toml [brand] section, desktop-build.sh VOLTUI_BRAND_NAME, and GitHub Actions/CNB release naming.
Use when tasks involve 西谷AI (Xigu AI) internal operations, 西谷智灯暗涌系统 product strategy, Chinese AI market context, local regulations, or fork-specific workflow decisions. Covers upstream sync strategy, release workflow, internal tooling, and product-market-fit decisions for the 西谷智灯暗涌系统 coding agent.
Design and review REST, OpenAPI, GraphQL, webhook, and internal service APIs. Use for contracts, versioning, idempotency, pagination, errors, auth, and SDK ergonomics.
Design and review system architecture, module boundaries, data flow, scalability, reliability, and migration plans.