القائمة
Use when user asks what ACC remembers, wiki health, or memory looks broken. Not Codex built-in /memories.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | wiki |
| description | Use when user asks what ACC remembers, wiki health, or memory looks broken. Not Codex built-in /memories. |
Reply rule:
/memories or ~/.codex/memories/Memory is automatic. Hooks write wants, decisions, open work, and next steps. SessionStart injects NOW + top lessons. User never needs a memory command in normal use.
.codex/anyone-can-code/memory/
NOW.md # live state (auto every turn)
raw/ # sources; never rewrite
notes/ # durable pages (auto + backup tools)
wiki/index.md # catalog
wiki/log.md # what changed
Triggers: what did we decide · what do you remember · status of memory
wiki_brief then retrieve_context.$status is fine for live Goal/Next.Triggers: clean memory · wiki health · lint wiki · memory broken
lint_wiki or run python3 scripts/memory_doctor.py.rebuild_index after fixes./hooks, trust
anyone-can-code, restart Codex (repeat after plugin update).Triggers: user explicitly says force-save this lesson despite auto memory
store_feedback with kind. Confirm path.Triggers: file this source into raw
ingest_raw with consent=true.raw/.When this skill's job is finished:
Use when a plan or concrete tasks exist and user said build/go/implement. Not to invent scope or claim done without verify.
Use when goal/spec is clear and you need ordered tasks before writing code. Not while still clarifying.
Use when about to claim done/works/fixed, or user asks test/check/prove. Run evidence; not for pure planning chat.
Use when another installed plugin/skill may do the job better, or to route specialists. ACC stays workflow owner.
Use when user wants an explicit recorded decision or blocker saved to artifacts. Not silent monitoring.
Use when request is too vague to plan or build. Not when goal and constraints are already clear.