菜单
Keep remem binary, Cargo, Codex plugin, release manifest, and npm wrapper versions synchronized. Use when changing package.version, release metadata, plugin runtime behavior, npm wrapper behavior, or when CI/check_plugin_version_sync.py or check_version_bump.py fails.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | remem-plugin-version-sync |
| description | Keep remem binary, Cargo, Codex plugin, release manifest, and npm wrapper versions synchronized. Use when changing package.version, release metadata, plugin runtime behavior, npm wrapper behavior, or when CI/check_plugin_version_sync.py or check_version_bump.py fails. |
Use this skill for changes that affect the shipped remem binary, Codex plugin
runtime, or npm wrapper. The goal is to keep all release surfaces consistent and
avoid a plugin that resolves a stale or incompatible runtime.
Keep these synchronized when the binary version changes:
Cargo.tomlCargo.lockplugins/remem/.codex-plugin/plugin.jsonplugins/remem/runtimes/remem-releases.jsonnpm/remem/package.jsonscripts/ci/check_plugin_version_sync.py requires the Rust package, plugin
manifest, release manifest, and npm wrapper package versions to match. A binary
version bump must update the npm package version even when npm wrapper behavior
is unchanged.
Read these before editing plugin runtime behavior:
plugins/remem/README.mdplugins/remem/skills/remem/SKILL.mdplugins/remem/scripts/remem-runtime.jsplugins/remem/scripts/remem-runtime.test.jsnpm/remem/scripts/install.jsnpm/remem/scripts/install.test.jsgit status --short and identify whether the PR changes binary-impacting
files: src/, migrations/, or Cargo.lock.Cargo.toml package.version.Cargo.lock so the remem-ai package version matches.plugins/remem/.codex-plugin/plugin.json to the same version.plugins/remem/runtimes/remem-releases.json so it contains exactly the
same version key and a base_url ending in /releases/download/v<version>.npm/remem/package.json to the same version. For npm-only metadata or
wrapper behavior changes, update this file without bumping the binary only
when check_plugin_version_sync.py still passes.REMEM_BINARY and plugin-managed runtime
paths are valid; do not silently adopt remem from PATH.Run these focused checks after version or plugin-runtime changes:
python3 scripts/ci/check_plugin_version_sync.py
node --test plugins/remem/scripts/remem-runtime.test.js plugins/remem/apps/remem/server.test.js npm/remem/scripts/install.test.js
python3 scripts/ci/check_version_bump.py origin/main HEAD
For Rust runtime changes, also run:
cargo fmt --check
cargo check
cargo test
check_plugin_version_sync.py fails, update all listed version files
together. Do not bypass the check with environment flags.check_version_bump.py fails, either bump Cargo.toml or prove the changed
file is not binary-impacting and update the gate separately.REMEM_ALLOW_VERSION_MISMATCH=1 only for explicit local debugging, never
as a PR validation substitute.Use when the user asks Codex to recall prior project context, save durable decisions or bug fixes, inspect remem memory health, or activate remem automatic memory hooks from the Codex plugin.
Use when turning an approved SpecRail product and technical spec into the numbered `tasks.md` plan. Creates stable task IDs, owners, done-when conditions, verification commands, dependencies, and handoff notes without implementing the tasks.
Use before reporting a SpecRail PR as merge-ready. Collects read-only PR evidence, runs the offline PR gate, checks linked work, current head SHA, CI, review decision, review threads, merge state, and human merge authorization without merging.
Use when performing an advisory SpecRail PR review. Checks linked issue/spec evidence, route gates, verification evidence, review-thread state, human-gate preservation, and implementation quality without granting final approval or merging.
Use as the router/startup skill when working in a repository that adopts SpecRail for issue-first, spec-first, AI-assisted development. Routes triage, spec writing, task planning, implementation, PR review, CI diagnosis, PR gates, release notes, and spec-vs-implementation checks to focused SpecRail skills while preserving locale and human-gate boundaries.
Use when writing or updating a SpecRail product spec for a linked issue. Produces the numbered `product.md` spec from the locale-appropriate template, focusing on user-facing behavior, goals, non-goals, and acceptance criteria without implementation detail.