메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | remem |
| description | 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. |
Remem gives Codex durable project memory through the remem MCP server. Use it when the answer depends on prior sessions, project preferences, saved decisions, workstreams, or memory health.
search results first, then call get_observations for selected IDs when exact content is needed.search_raw only when curated search misses an exact phrase or chat transcript detail.Save a durable memory after:
Use the active repo/workspace project plus a stable topic_key so repeated saves update the same memory instead of creating duplicates.
For project memories, pass project as the active repo/workspace path and pass
branch when it is known. Use scope: "global" only for explicit cross-project
user preferences.
The plugin exposes MCP tools as soon as Codex loads .mcp.json and the runtime
manager can resolve a matching remem binary. Automatic context injection and
Stop summarization require explicit activation. The plugin does not ship
auto-loaded hook definitions because Codex hook runners do not always provide a
plugin root environment. Activation writes verified host-level hooks through
remem install --target codex --hooks-only.
For a local repo checkout, activate with:
cargo build --release
node plugins/remem/scripts/remem-runtime.js install
node plugins/remem/scripts/activate-codex.js --dry-run
node plugins/remem/scripts/activate-codex.js
remem doctor
remem status
If the plugin cannot find the binary, build or explicitly point at remem first:
cargo build --release
REMEM_BINARY="$PWD/target/release/remem" node plugins/remem/scripts/activate-codex.js --dry-run
The wrapper rejects stale remem binaries by default. Use REMEM_ALLOW_VERSION_MISMATCH=1 only for explicit local debugging.
For local GUI testing from this repo, run:
cargo build --release
node plugins/remem/scripts/remem-runtime.js install
node plugins/remem/apps/remem/server.js --port 5577
The app exposes runtime status, memory counts, search/detail, explicit save, and
activation dry-run views. Treat this as a local Apps SDK surface until a real
.app.json app id is available.
After installing or updating the plugin, start a new Codex thread so skills and MCP tools are reloaded.
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.
Use when writing or updating a SpecRail technical spec for a linked issue. Produces the numbered `tech.md` spec from the locale-appropriate template, translating accepted product behavior into design, affected files, risks, verification, and rollback without starting implementation.