Menu
Use when updating npm dependencies, toolchain versions, or container base images in the CommonEx backend project.
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.
Based on SOC occupation classification
Use when updating dependency or container versions across CommonEx projects and the work should start with internet verification, a per-bundle summary plus full release-note output, a user selection gate, and then implementation.
Use when updating mobile (Android/iOS) or KMM dependency versions, Gradle toolchain versions, or related mobile build inputs in the CommonEx android KMM project.
Use when updating Docker image tags, custom infrastructure build inputs, or observability stack versions in the CommonEx infra project.
Use when updating npm dependencies, UI library versions, framework versions, or container runtime images in the CommonEx web project.
Prepare a CommonEx mobile release (Android + iOS): bump version on both platforms, generate Android baseline profiles, and create/push a release tag. Use when the user asks to prepare a mobile release or run the release SOP. Requires RELEASE_VERSION, PATCH, RUN_FROM (repo-root or android/), and SHELL.
Propose and apply updates to repo docs, skill instructions, and agent guidance based on session-verified knowledge and user signals about agent behavior. Use when the user asks to sync/update instructions, AGENTS.md, README.md, docs/*, project docs, or skill docs with new knowledge or behavior feedback learned in the current session.
| name | update-backend-dependencies |
| description | Use when updating npm dependencies, toolchain versions, or container base images in the CommonEx backend project. |
Follow .agents/skills/update-dependency-batch for the mandatory four-phase workflow.
Read versions from:
backend/package.jsonbackend/package-lock.jsonbackend/DockerfileUse exact versions only. Do not introduce ^ or ~.
Use primary sources:
npm outdated for a first pass on installed vs wanted vs latestnpm view <package> version when you need the exact current registry latestnode:24-alpine3.23Prefer official NestJS, Fastify, OpenTelemetry, TypeORM, TypeScript, ESLint, Jest, and Node release notes when relevant.
Default bundle boundaries:
@nestjs/* packages, @nestjs/swagger, @nestjs/terminus, @nestjs/typeorm, and @nestjs/testing when the same upstream release line expects them togetherfastify, @fastify/*, and fastify-plugin@opentelemetry/* packages and any recursively referenced instrumentation packagestypescript, @typescript-eslint/*, eslint, @eslint/*, globals, eslint-config-prettier, eslint-plugin-prettier when peer constraints require itjest, ts-jest, @types/jest, supertest, and related type packages when peer versions are coupledbackend/Dockerfile base image updatesSingle-package updates are fine when there is no peer or framework coupling.
Follow .agents/skills/update-dependency-batch (one ## N — … section per bundle: Summary, then full numbered release notes). Stop after the proposal; do not edit manifests until the user selects bundles.
When the user selects bundles in a follow-up message:
package.json, regenerate package-lock.json, and keep pinned exact versionsFollow project's validation instructions.
If a selected bundle changes migrations, transport behavior, or runtime bootstrap, call that out explicitly in the report.