elie222/inbox-zero

update-packages

Update workspace packages while respecting the repo's pinned package list in .ncurc.cjs. Use when the user asks to update dependencies or refresh package versions.

First seen Mar 10, 2026

Installation

$ npx skills add elie222/inbox-zero --skill update-packages

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from elie222/inbox-zero · top by installs.

npx skills add elie222/inbox-zero

Browse all from elie222/inbox-zero

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 12.1K
License LICENSE
Default branch main
Open issues 96
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,306 B
  • docs SUMMARY.md 186 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 34 installs

SKILL.md

Update Packages

Use this workflow when updating dependencies in this repo.

Steps

  1. Check the pinned package list in .ncurc.cjs. Do not upgrade packages listed there.
  2. Keep the repo on Node 24. If you change Node runtime settings, update .nvmrc, engines.node, @types/node, Dockerfiles, and CI together.
  3. Update manifests across the workspace:
pnpm dlx npm-check-updates -u -ws
  1. Refresh the lockfile and install updated packages:
pnpm install
  1. Verify the update:
pnpm test
pnpm lint

Notes

  • npm-check-updates reads .ncurc.cjs, so the reject list is applied during the manifest update.
  • pnpm install may also bump the root packageManager field and regenerate pnpm-lock.yaml.
  • Do not run pnpm dev or pnpm build unless the user explicitly asks.
  • Keep @hookform/resolvers in the .ncurc.cjs reject list and pinned to 4.1.0 while apps/web remains on [email protected]. The 5.x resolver line imports zod/v4/core, which has caused local Next.js/Turbopack resolution failures even though the app code still uses Zod 3.