菜单
Use when updating Docker image tags, custom infrastructure build inputs, or observability stack versions in the CommonEx infra project.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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 npm dependencies, toolchain versions, or container base images in the CommonEx backend 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-infra-dependencies |
| description | Use when updating Docker image tags, custom infrastructure build inputs, or observability stack versions in the CommonEx infra project. |
Follow .agents/skills/update-dependency-batch for the mandatory four-phase workflow.
Read versions from:
infra/docker-compose-prod.ymlinfra/nginx/Dockerfileinfra/otel-collector/Dockerfileinfra/otel-collector/manifest.yamlinfra/nginx/nginx-prod.confinfra/otel-collector/otel-collector-config.yamlUse official or primary sources:
docker-compose-prod.ymlNGINX_VERSIONOPENSSL_VERSIONnginxinc/nginx-otel releases for NGINX_OTEL_VERSIONOTEL_VERSIONFor custom-built images, verify both the base image and the source-built component versions.
Default bundle boundaries:
NGINX_VERSION, OPENSSL_VERSION, NGINX_OTEL_VERSION, and any required config changes driven by upstream behaviorOTEL_VERSION and any manifest or config changes required by the selected collector releasevictoriametrics/victoria-metrics and victoriametrics/victoria-traces when a coordinated upgrade is recommended upstreamgrafana/grafana plus provisioning adjustments if release notes require thempostgres image updatescertbot/certbot updatesIndependent image bumps are acceptable when upstream compatibility does not couple them.
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:
Follow project's validation instructions.
If an image tag update was selected for a service without a custom Dockerfile, config validation is the minimum gate unless the user asks for a live pull or deploy check.