菜单
Run the @trycourier package test suites (the "🧪 Run Tests" launch config) — all packages at once or a single package. Use when asked to run tests, verify a change is covered, or reproduce a CI test failure locally for courier-js, courier-react, courier-react-17, courier-ui-inbox, or courier-ui-toast.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Manage versioning for the @trycourier packages with changesets — create a changeset describing a version bump after changing package source, and bump package versions for release with `yarn changeset version`. Use when modifying @trycourier/*/src and a release-tracking changeset is needed, or when cutting a release locally / running the "Version Packages" step by hand.
Diagnose and drive the courier-web npm release pipeline — the Release workflow on main, the changesets "Version Packages" PR (changelogs + version bumps), and OIDC publishing to npm. Use when a Release run fails, packages didn't appear on npm after merging Version Packages, publishing hits ENEEDAUTH, or someone asks why the changelogs/release didn't kick off after a merge.
Change or add a themable style (border, color, shadow, radius, font) on a Courier UI web component — inbox, toast, preferences, or core. Use when adjusting a component's default look, adding a new theme property, or fixing a style that doesn't render in light or dark mode.
Keep the framework-SDK showcase example apps (react-latest, react-17, vue, and angular) at feature parity — the same set of demo pages and routes, one per SDK. Use whenever you add, change, or remove a demo in one showcase example (a new route/page, a themed variant, a custom-renderer demo, etc.) so the change is mirrored across the others, or when auditing that the showcases are in sync.
Checklist for adding a new example app under examples/* so it's runnable and discoverable. Use whenever you create a new example app (any new examples/<name> workspace) — it MUST be registered in .vscode/launch.json's "🚀 Run Example App" picker, and there are a few other wiring steps. Apply this any time you scaffold a new example.
Check or update the committed API reports for the @trycourier packages (API Extractor reports under api/*.api.md). Use when CI's "Build packages and check API changes" job fails on an API diff, when you intentionally changed a package's public API surface and need to refresh the committed report, or to verify locally that the reports are in sync before pushing.
| name | run-tests |
| description | Run the @trycourier package test suites (the "🧪 Run Tests" launch config) — all packages at once or a single package. Use when asked to run tests, verify a change is covered, or reproduce a CI test failure locally for courier-js, courier-react, courier-react-17, courier-ui-inbox, or courier-ui-toast. |
This is the headless equivalent of the 🧪 Run Tests VSCode launch config.
From the repo root:
yarn test:all
This runs each package's test script concurrently (courier-js, courier-ui-inbox, courier-react, courier-react-17, courier-ui-toast, courier-ui-preferences).
yarn workspace @trycourier/courier-ui-inbox run test
Available test targets:
@trycourier/courier-js@trycourier/courier-react@trycourier/courier-react-17@trycourier/courier-ui-inbox@trycourier/courier-ui-toast@trycourier/courier-ui-preferencesThe test runners are Jest-based. Pass a filename pattern after --:
yarn workspace @trycourier/courier-ui-inbox run test -- info-state-style-scoping
Several suites import sibling packages by their built output. If you see:
Cannot find module '@trycourier/courier-js' from 'src/datastore/inbox-datastore.ts'
the dependency package hasn't been built. Build it (or all packages) before running tests:
yarn workspace @trycourier/courier-js run build
# or, for a clean full reset, see the sync-packages skill:
yarn build-packages
See the sync-packages skill for details.
yarn@1 (classic).courier-ui-core has no tests (its test script is a no-op) — exercise its components through courier-ui-inbox tests instead.