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.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
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
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-26
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!