update deps

Engineering Community

Skill notes

Pre-loaded data

!`PM="npm"; if [ -f bun.lockb ] || [ -f bun.lock ]; then PM="bun"; elif [ -f pnpm-lock.yaml ]; then PM="pnpm"; elif [ -f yarn.lock ]; then PM="yarn"; fi; echo "=== PACKAGE_MANAGER ==="; echo "$PM"; echo "=== DATE ==="; date +%Y-%m-%d; echo "=== OUTDATED ==="; if [ "$PM" = "pnpm" ]; then pnpm outdated --json 2>/dev/null || true; elif [ "$PM" = "bun" ]; then bun outdated 2>/dev/null || true; elif [ "$PM" = "yarn" ]; then yarn outdated --json 2>/dev/null || true; else npm outdated --json 2>/dev/null || true; fi; echo "=== AUDIT ==="; if [ "$PM" = "pnpm" ]; then pnpm audit --json 2>/dev/null || true; elif [ "$PM" = "npm" ]; then npm audit --json 2>/dev/null || true; elif [ "$PM" = "yarn" ]; then yarn audit --json 2>/dev/null || true; fi; echo "=== OVERRIDES ==="; node -e "const p=require('./package.json'); console.log(JSON.stringify({overrides:p.overrides,pnpmOverrides:p.pnpm?.overrides,reso

Arguments

If arguments were passed (e.g., /update-deps react, /update-deps major): If the argument is major, minor, or patch — filter to only that update type Otherwise, treat it as a package name filter — only audit packages whose name contains the argument If no arguments, audit all outdated packages Arguments: $ARGUMENTS

Step 1 — Parse and categorize

From the pre-loaded data above, build a list of every outdated package with: Package name Current version → Wanted version (within semver range) → Latest version In-range: yes if wanted > current (updatable without changing package.json), no if requires range bump dependency or devDependency (use DEV_DEPS list)

Step 2 — Research + impact analysis (single pass, parallel agents)

Launch parallel Agent calls. Each agent researches the changelog AND checks codebase impact in one pass. Grouping strategy (target: max 10-12 agents total): One agent per package for major updates with breaking changes expected Group by ecosystem for minor updates: all @tanstack/* together, all @radix-ui/* together, all @sentry/* together, all eslint-related together, etc. One agent per group.

Agent prompt template

Each agent MUST receive and follow these instructions: Part A — Research (for each package assigned): Find changelog info by trying these sources in order — stop as soon as you get meaningful results: npm registry metadata: run npm view [package-name] repository.url homepage via Bash to get the repo URL and homepage GitHub Releases page: if repo is on GitHub, WebFetch on https://github.com/[org]/[repo]/releases — this is where most projects document breaking changes and migration guides

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@viclafouch · MIT
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js · Bun
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1 — Parse and categorize

From the pre-loaded data above, build a list of every outdated package with: Package name Current version → Wanted version (within semver range) → Latest version In-range: yes if `wanted > current` (updatable without changing `package.json`), no if requires range bump `dependency` or `devDependency` (use DEV_DEPS list)

02
Step 2 — Research + impact analysis (single pass, parallel agents)

Launch parallel Agent calls. Each agent researches the changelog AND checks codebase impact in one pass. Grouping strategy (target: max 10-12 agents total): One agent per package for major updates with breaking changes expected Group by ecosystem for minor updates: all `@tanstack/*` together, all `@radix-ui/*` together, all `@sentry/*` together, all `eslint`-related together, etc. One agent per group.

03
Step 3 — Create the plan file

After ALL agents complete, write `plan-update-deps-DATE.md` (one single write, using today's date from pre-loaded data). Place it in whichever plan directory the project uses (check for `.claude/plans/`, `docs/`, or project root — prefer an existing directory; create `.claude/plans/` as default if none exists). Structure:

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.