Run any Skill in Manus with one click

update-packages

Stars11,687

Forks1,446

UpdatedApril 10, 2026 at 22:05

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

elie222

elie222/inbox-zero

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	update-packages
description	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.

Update Packages

Use this workflow when updating dependencies in this repo.

Steps

Check the pinned package list in .ncurc.cjs. Do not upgrade packages listed there.
Keep the repo on Node 24. If you change Node runtime settings, update .nvmrc, engines.node, @types/node, Dockerfiles, and CI together.
Update manifests across the workspace:

pnpm dlx npm-check-updates -u -ws

Refresh the lockfile and install updated packages:

pnpm install

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 zod@3.25.76. 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.

More from this repository

same repository

testing

elie222/inbox-zero

Guidelines for testing the application with Vitest, including unit tests, integration tests (emulator), AI tests, and eval suites for LLM features

2026-06-2411.7k

cloud-dev-environment

elie222/inbox-zero

Cursor Cloud VM setup and service startup instructions for local development

2026-06-0411.7k

llm

elie222/inbox-zero

Guidelines for implementing LLM (Language Model) functionality in the application

2026-06-0411.7k

code-simplifier

elie222/inbox-zero

Simplify and refine recently modified code for clarity, consistency, and maintainability while preserving exact behavior. Use when asked to simplify, polish, refactor lightly, or clean up current-session changes before review or PR.

2026-05-0511.7k

create-pr

elie222/inbox-zero

Commit changes and open a pull request with safe metadata

2026-04-3011.7k

review-ai-prompt-changes

elie222/inbox-zero

Review prompt and tool-description changes in a branch or PR. Use when asked to audit system prompts, prompt builders, tool descriptions, prompt inputs, or nearby evals/tests; summarize what changed; identify guidance that feels eval-shaped or too heavy for product use; and find repeated instructions between the main prompt and tool descriptions.

2026-04-2211.7k

name	update-packages
description	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.

Update Packages

Use this workflow when updating dependencies in this repo.

Steps

Check the pinned package list in .ncurc.cjs. Do not upgrade packages listed there.
Keep the repo on Node 24. If you change Node runtime settings, update .nvmrc, engines.node, @types/node, Dockerfiles, and CI together.
Update manifests across the workspace:

pnpm dlx npm-check-updates -u -ws

Refresh the lockfile and install updated packages:

pnpm install

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 zod@3.25.76. 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.