菜单
Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether session_start is useful.
| name | memorix-reasoning |
| description | Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered. |
Use reasoning memory for why a decision was made. Use ordinary memory for what happened.
| Situation | Prefer | CLI fallback |
|---|---|---|
| Store why a decision was made | memorix_store_reasoning | memorix reasoning store --entity <name> --decision "<decision>" --rationale "<why>" |
| Find earlier rationale | memorix_search_reasoning | memorix reasoning search --query "<topic>" |
| Need a stable evolving topic key | memorix_suggest_topic_key | memorix memory suggest-topic-key --type decision --title "<title>" |
| Link rationale to commit evidence | relatedCommits on reasoning store | memorix reasoning store ... --relatedCommits <sha> |
memorix_store as how-it-works, what-changed, or problem-solution.