memorix-reasoning
SolidUse when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.
AI & Automation 583 stars
45 forks Updated today Apache-2.0
Install
Quality Score: 89/100
Stars 20%
Recency 20%
Frontmatter 20%
Documentation 15%
Issue Health 10%
License 10%
Description 5%
Skill Content
# 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`.
Details
- Author
- AVIDS2
- Repository
- AVIDS2/memorix
- Created
- 5 months ago
- Last Updated
- today
- Language
- TypeScript
- License
- Apache-2.0
Similar Skills
Semantically similar based on skill content — not just same category
Code & Development Solid
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
583 Updated today
AVIDS2 AI & Automation Featured
memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
583 Updated today
AVIDS2 AI & Automation Solid
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
583 Updated today
AVIDS2