/memorix-reasoning
Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.
$ npx -y skills add AVIDS2/memorix --skill memorix-reasoning --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/memorix-reasoning
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.
SKILL.md
memorix-reasoning.SKILL.mdname: memorix-reasoning
description: Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.
Memorix Reasoning
Use reasoning memory for why a decision was made. Use ordinary memory for what happened.
Tool Router
| 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>` |
Use Reasoning When
- The answer depends on alternatives considered, constraints, expected outcomes, or accepted risks.
- A future agent may otherwise reopen the same debate.
- The user chose a direction and the reason matters more than the implementation details.
- A Git Memory entry says what changed, but not why it changed.
Do Not Use Reasoning For
- Simple progress notes.
- Mechanical refactors with no decision.
- Facts that belong in `memorix_store` as `how-it-works`, `what-changed`, or `problem-solution`.
Read more
name: memorix-reasoning description: Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.
Memorix Reasoning
Use reasoning memory for why a decision was made. Use ordinary memory for what happened.
Tool Router
| 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>` |
Use Reasoning When
- The answer depends on alternatives considered, constraints, expected outcomes, or accepted risks.
- A future agent may otherwise reopen the same debate.
- The user chose a direction and the reason matters more than the implementation details.
- A Git Memory entry says what changed, but not why it changed.
Do Not Use Reasoning For
- Simple progress notes.
- Mechanical refactors with no decision.
- Facts that belong in `memorix_store` as `how-it-works`, `what-changed`, or `problem-solution`.
Open-source cross-agent memory layer for coding agents via MCP. Compatible with Claude Code, Codex, Cursor, Windsurf, Gemini CLI, Antigravity, OpenClaw, Hermes Agent, Oh-my-Pi, Pi, Copilot, Kiro, OpenCode, and Trae.
Repo: AVIDS2/memorix
Other skills on memorix.
- /memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
Open skill - /memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
Open skill - /memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
Open skill - /memorix-orchestrate
Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.
Open skill - /memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether session_start is useful.
Open skill - /memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
Open skill