local-package
$
npx mdskill add ClipboardHealth/core-utils/local-packageLink and unlink packages locally without publishing.
- Test package changes across repositories instantly.
- Integrates with Clipboard's internal CLI and yalc.
- Executes nx builds and updates package.json automatically.
- Delivers results by modifying local dependencies.
SKILL.md
.github/skills/local-packageView on GitHub ↗
--- name: local-package description: Use Clipboard's internal CLI to link and unlink @clipboard-health packages across repositories for local development. Use when testing local package changes, linking @clipboard-health packages between repos, or using the cbh CLI local-package command. --- # Local Package Development Use Clipboard's internal CLI (`@clipboard-health/cli`) to test package changes across repositories without publishing. The `cbh local-package` command wraps [yalc](https://www.npmjs.com/package/yalc) to simplify linking packages between sibling repositories. ## Prerequisites See the [CLI README](https://github.com/ClipboardHealth/cbh-core/tree/main/packages/cli#local-package) for setup instructions. ## Commands ### Link packages From the consuming repository, link packages from sibling repos: ```bash cbh local-package link --packages <package-names...> ``` Example: ```bash cbh local-package link --packages util-ts ``` This will: 1. Find the package in sibling `packages/*` directories 2. Build the package with nx 3. Push the built package to yalc 4. Update your `package.json` to use the yalc version ### Unlink packages After testing, restore the published package versions: ```bash cbh local-package unlink --packages <package-names...> ``` Example: ```bash cbh local-package unlink --packages util-ts ``` ## Workflow Example To test changes to `util-ts` in `cbh-mobile-app`: 1. Make changes to `util-ts` in `core-utils` 2. From `cbh-mobile-app` root, run: ```bash cbh local-package link --packages util-ts ``` 3. Test your changes in `cbh-mobile-app` 4. When done, unlink: ```bash cbh local-package unlink --packages util-ts ``` ## Troubleshooting - **Package not found**: Ensure the package exists in a sibling repo's `packages/` directory - **Build fails**: The package must have a valid nx build target - **Changes not reflected**: Run `npm install` after linking to pull in the yalc version
More from ClipboardHealth/core-utils
- adversarial-reviewPerform an adversarial review of proposed work. Use ONLY when the user explicitly types /adversarial-review. Never auto-trigger, even if the user mentions reviewing, questioning, or challenging their approach.
- clipboard-testingEnd-to-end testing playbook for Clipboard Health changes. Use when the user wants to verify, exercise, or set up test data for a backend or frontend change against a live environment — "test my change end-to-end", "verify this works in dev", "create a test workplace / worker / shift", "get a shift through to paid / invoiced", "prove the API change works". Defaults to the `development` AWS environment, API-first (cbh CLI tokens + curl). The skill knows enough to run the core happy-path flow (workplace → worker → shift → clock in/out → pay → invoice) autonomously; for anything else, it orients around the codebase and asks the user for missing directories.
- cognito-user-analysisUse when looking up Cognito user details by sub UUID, finding duplicate accounts sharing phone or email, analyzing which duplicates to keep vs delete, or fixing orphaned UNCONFIRMED signups. Symptoms include 403 Forbidden on login, multiple accounts for same phone, backend sync issues.
- datadog-investigateInvestigate production issues by querying Datadog logs, metrics, and APM traces, then correlating findings with the codebase. Use this skill whenever the user mentions production errors, Datadog, observability, log investigation, latency spikes, error rate increases, 500s, trace IDs, monitor alerts, or wants to debug any service issue in a deployed environment.
- flaky-test-debuggerDebug and fix flaky tests including Playwright E2E, NestJS service/integration, React component, and unit tests. Use this skill when investigating intermittent test failures, triaging flaky tests, or fixing test instability.
- interview-featureUse when clarifying requirements for a feature ticket. Iteratively researches and interviews the user until the problem is well-understood, then produces a structured problem brief. Dispatched by write-feature-ticket when context is insufficient.
- investigate-ticketUse when investigating a bug, incident, or issue before implementation. Researches codebase, queries Datadog, and presents structured findings with handoff options. Also use when asked to "look into" or "investigate" something.
- seed-dataTrigger seed data generation for test environments via GitHub Actions. Use when asked to seed, create test data, or set up HCPs/facilities/shifts.
- write-bug-ticketUse when creating a Linear bug report ticket from conversation context, investigation findings, or user-provided evidence. Focuses on structuring and writing — not investigating.
- write-feature-ticketUse when creating a Linear feature request ticket from conversation context, a brief description, or code/PR analysis. Interviews the user for clarity when context is insufficient.