shared-release-workflow
Enforces the two-stage shared→backend workflow (publish shared first, then consume from registry). Use when changing both shared/ and backend/ or when shared package versioning/publishing is involved.
安装与使用
请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求,再添加到工作流。
查看来源 ↗使用指南技能说明
Shared release workflow
Use this skill when you are asked to:
- Add new exports to
shared/and use them inbackend/. - Bump
@piquet-h/sharedand ensure backend installs from the registry. - Prevent “combined PR touches shared + backend and breaks CI” situations.
Rules
- Never change backend to depend on
file:../shared. - If behavior requires new shared exports, split into two PRs:
- PR 1:
shared/only (bump version, publish) - PR 2: backend integrates the published version
- PR 1:
Helper script
-
scripts/detect-cross-package.mjs— detects when the current diff touches bothshared/andbackend/.
Use this script as an early warning. It is not a replacement for code review.
Last reviewed: 2026-01-15
使用示例
查看来源仓库中的使用示例与配置说明。
查看来源 ↗来源历史
- 收录时间
- 2026-01-20
- 索引更新时间
- 2026-01-26
- Branch
- main
收录与同步日期属于本站记录。源码修改历史请查看来源仓库。
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!