菜单
Show Memoir status for the current Codex project: store path, branch, commit count, memory count, and namespaces. Use when the user asks for Memoir status, whether Memoir is working, what store or branch is active, or why memories are not appearing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Populate or refresh a persistent, high-level project snapshot in memoir. In a git repo this writes `codebase:onboard` (code-shape: modules, goals, rules, lessons) — use when the user asks for onboarding / a codebase tour ('what does this project do', 'give me a codebase overview', 'onboard me to this repo') or explicitly asks to refresh Memoir onboarding. In a non-git folder this writes `project:onboard` (file-shape: per-file structured blobs) using deterministic stdlib extractors instead of LLM passes — use for writing, video editing, bookkeeping, and other mixed-media projects. Snapshot contents seed future sessions via SessionStart injection. Skip for ordinary recall (use memory-recall) or trivial one-file questions.
Explicitly save a user-requested memory to Memoir now. Use when the user says remember, save, store, capture, or record a durable preference, decision, rule, fact, or note. Pick a taxonomy path with Codex when none is provided, always write with `memoir remember -p`, and never use legacy unpathed `memoir remember`.
Launch or reopen the Memoir web UI for the current Codex project store. Use when the user asks to open, browse, inspect, visualize, or view Memoir memories in the UI. Starts the safe readonly, no-LLM UI through the plugin helper and reports the URL, PID, and store.
Recall facts from past sessions via memoir for questions or tasks that may depend on prior preferences, decisions, conventions, or knowledge. Use one fast summarize/get pass by default, exclude metrics unless requested, never call legacy `memoir recall`, and defer repo-structure onboarding questions to memoir-onboard.
Populate or refresh a persistent, high-level project snapshot in memoir. In a git repo this writes `codebase:onboard` (code-shape: modules, goals, rules, lessons) — use when: (1) the user asks for onboarding / a codebase tour ('what does this project do', 'give me a codebase overview', 'onboard me to this repo'); (2) the user explicitly runs `/memoir:onboard` or `/memoir:onboard --force`. In a non-git folder this writes `project:onboard` (file-shape: per-file structured blobs) using deterministic stdlib extractors instead of LLM passes — use for writing, video editing, bookkeeping, and other mixed-media projects. Snapshot contents seed future sessions via SessionStart injection. Skip for ordinary recall (use memory-recall) or trivial one-file questions.
Recall facts from past sessions via memoir. STORE PATH: ALWAYS compute first via `STORE=$(bash "$CLAUDE_PLUGIN_ROOT/scripts/derive-store-path.sh")` (or `$MEMOIR_STORE`). Pass `-s "$STORE"` on every call — never rely on memoir's connected default (frequently stale). PROCEDURE (single-shot default): ONE `summarize --depth 3 -n default` → pick at most 5–7 keys → batch `get`. Only escalate to drill (batched `--keys`) if the depth-3 response shows `total_memories > 1000` AND the query is broad. Never call `summarize --depth 1` separately — `--depth 3` already returns count + full key listing. EXCLUDE `metrics.*` unless args contain `--include-metrics`. NEVER shell out to `memoir recall` (legacy LLM-bundled, slow, requires OPENAI_API_KEY). First reply line MUST be a mode marker `[mode=get|fast|drill|flat|blame|diff]`. DEFAULT ON: invoke for any question or task that may depend on past preferences, decisions, conventions, or knowledge — questions touching prior state, meta/overview asks, design/implementation prompt
| name | memoir-status |
| description | Show Memoir status for the current Codex project: store path, branch, commit count, memory count, and namespaces. Use when the user asks for Memoir status, whether Memoir is working, what store or branch is active, or why memories are not appearing. |
Use this skill for Memoir diagnostics and status checks.
Run:
PLUGIN_ROOT="${PLUGIN_ROOT:-}"
if [ -z "$PLUGIN_ROOT" ]; then
PLUGIN_ROOT=$(find "${CODEX_HOME:-$HOME/.codex}/plugins" -path '*/.codex-plugin/plugin.json' -print 2>/dev/null \
| while IFS= read -r manifest; do
python3 - "$manifest" <<'PY'
import json, sys
from pathlib import Path
path = Path(sys.argv[1])
try:
data = json.loads(path.read_text())
except Exception:
raise SystemExit(0)
if data.get("name") == "memoir":
print(path.parent.parent)
PY
done | head -n 1)
fi
if [ -z "$PLUGIN_ROOT" ] || [ ! -x "$PLUGIN_ROOT/scripts/status-cmd.sh" ]; then
echo "Memoir Codex plugin not found" >&2
exit 127
fi
bash "$PLUGIN_ROOT/scripts/status-cmd.sh"
Summarize the JSON in one short paragraph: store path, current branch, memory count, commit count, and namespaces. If the user is debugging missing memories, also explain that the Codex plugin uses a derived store under ~/.memoir/<slug> unless MEMOIR_STORE is set, so bare memoir status from the project directory may inspect a different store.