菜单
Publish all packages to npm with synchronized versioning (Lerna). Use when the user wants to release, publish, or cut a new version of the packages.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Two-stage panel review of a task file BEFORE implementation. Stage 1 (framing & scope — archaeology/altitude, YAGNI + intermediate-goal scoping, product vision) is resolved and the file edited FIRST; Stage 2 (conformance — architecture/mesh, security, test-strategy) then reviews the cleaned file. Each stage adversarially verifies findings before you see them. Use when a task file is ready for design review, when the user says "review the X task", or before saying "go" on implementation.
The "go" procedure — implement a reviewed task file phase-by-phase, then fan out adversarial verifiers that check each phase against its own success criteria + .claude/rules/ (which /code-review can't do because it doesn't know the task file). Use when the user says "go"/"implement"/"build" on a task file that has already been through /review-task (or equivalent design review).
Convert audited @skip-check code blocks into @check-example annotations or flag @skip-check-approved candidates for human approval. Use after /doc-example-audit, before publishing docs.
Manually-invoked bedtime self-improvement pass (v0, thin). Picks ONE easy-to-review candidate from tasks/nightly/backlog.md, does a small findings-only review, and writes a triage-optimized morning digest to tasks/nightly/<date>.md. Invoke EXPLICITLY at bedtime via /nightly-pass — never auto-trigger.
Audit @skip-check annotations in website docs (.md/.mdx) — categorize each block and produce a prioritized conversion plan. Use before starting Phase 2 doc work.
Verify @skip-check-approved code examples against actual source code — catch stale or incorrect examples before release. Use as a pre-release check.
| name | release-workflow |
| description | Publish all packages to npm with synchronized versioning (Lerna). Use when the user wants to release, publish, or cut a new version of the packages. |
| argument-hint | ["dry-run|publish"] |
Publish all packages with synchronized versioning. This is the only time a build runs — publish scripts repoint package.json from src/ to dist/, build, publish, then revert (see .claude/rules/workflow.md § Releases and § No build during development).
/release-workflow <dry-run|publish>
All in /scripts/:
release-dry-run.sh - Test release without publishing (always run first)release.sh - Actual publishbuild-packages.sh - Compile TypeScript to dist/prepare-for-publish.sh - Modify package.json for publishrestore-dev-mode.sh - Revert to dev mode after publish/review-skip-check-approved main — verifies @skip-check-approved doc examples (excluded from automated testing) still match the source that's about to ship../scripts/release-dry-run.sh
Review output for issues before proceeding.
./scripts/release.sh