メニュー
Recall project context and present structured readback. Use when the user asks 'do you remember?', at session start, or when context seems lost.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/ActiveMemory/ctx --skill ctx-rememberコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
SKILL.md を表示中
| name | ctx-remember |
| description | Recall project context and present structured readback. Use when the user asks 'do you remember?', at session start, or when context seems lost. |
Recall project context and present a structured readback as if remembering, not searching.
Check that the context directory exists. If it does not, tell the
user: "No context directory found. Run ctx init to set up context
tracking, then there will be something to remember."
/ctx-agent: don't
re-fetch what you already have/ctx-history instead, which has list/show/export
subcommandsDo all of this silently: narrating the steps makes the readback feel like a file search rather than genuine recall:
Load context packet:
ctx agent
Read the files listed in the packet's "Read These Files" section (TASKS.md, DECISIONS.md, LEARNINGS.md, etc.)
List recent sessions:
ctx journal source --limit 3
Read the latest handover. Look under
.context/handovers/, sort by filename (timestamped
<TS>-<slug>.md; the newest is the lexicographically
last), and read its ## Summary and ## Next Session
sections as the authoritative recall surface. The
handover is the previous session's note to this one.
Skip only if .context/handovers/ is empty or absent.
Read postdated closeouts, if any. When
.context/ingest/closeouts/ exists, list closeouts whose
generated-at postdates the handover's generated-at
and read their ## What Changed sections. These are
per-pass audit notes the previous wrap-up did not get a
chance to fold into a handover. This step is read-only:
/ctx-remember does not run any editorial pass. If the
directory does not exist or holds no postdated entries,
skip the step.
Check knowledge health (read-only). Run:
ctx system check-knowledge --report
It prints nothing when every canonical root is within limits.
When it prints findings, surface them in the readback's
Knowledge health line: a foldable root suggests
/ctx-digest (fold the staging zone into themes); a heavy
page suggests splitting the theme or extracting it to tooling.
Suggest only — never run /ctx-digest or edit a file here.
If it prints nothing, omit the line.
Present the structured readback (see format below)
Present your findings as a structured readback with these sections:
Last session: Topic, date, and what was accomplished. Cite the most recent session from the session list.
Active work: Pending and in-progress tasks from TASKS.md. Use a brief list: one line per task with its status.
Recent context: 1-2 recent decisions or learnings that are relevant. Pick the most recent or most impactful.
Next step: Suggest what to work on next based on the active tasks, or ask the user for direction if priorities are unclear.
Knowledge health (only when ctx system check-knowledge --report printed findings): name the foldable roots and/or heavy
pages it reported and the suggested remedy (/ctx-digest, or
split/extract). Suggestion only; omit the line entirely when the
report was empty.
Last session (2026-02-07): We implemented the cooldown mechanism for
ctx agentto prevent redundant context loads.Active work:
- Add
--format jsonflag toctx status(pending)- Implement session cooldown (done)
- Write integration tests for journal import (in progress)
Recent context:
- Decided to use file-based cooldown tokens instead of environment variables (simpler, works across shells)
- Learned that Claude Code hooks run in a subprocess, so env vars set in hooks don't persist to the main session
Next step: The integration tests for journal import are partially done. Want to continue those, or shift to the JSON status flag?
"I don't have persistent memory, but let me check if there are any context files..."
"Let me look at the context files to see what's there. I found TASKS.md, let me read it..."
"I found some session files. Here's what they contain..."
After presenting the readback, check companion tool availability.
Skip this section entirely if companion_check: false is set in
.ctxrc: check by running ctx config status and looking for
the field value.
Companion tools enhance ctx skills with web search and code intelligence. They are optional but recommended. ctx names canonical implementations below; if your MCP toolchain provides equivalent capabilities through different servers (e.g. Firecrawl / Exa / Tavily for web search; sourcegraph-cody for code graph), use whatever you have connected.
| Capability | Canonical example | Smoke test for the canonical example |
|---|---|---|
| Web search with citations | Gemini Search | Call mcp__gemini-search__search_with_grounding with a simple query |
| Code knowledge graph | GitNexus | Call mcp__gitnexus__list_repos |
Check procedure:
"GitNexus index is stale: reindex with the repo's own entry point — a
make gitnexus-indextarget, an indexing script, or the steps in itsGITNEXUS.md— if it has one; otherwise rungitnexus analyze. (On hosts where the npm binary can't build, the repo-local Docker path is the reliable runner.)"
Present companion status as a one-line note after the readback only when there's something actionable (stale index). Absent tools produce no output; the agent uses its built-in capabilities transparently.
Before presenting the readback, verify: