memorix-reasoning

Solid

Use 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

View on GitHub

Quality Score: 89/100

Stars 20%
92
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
61
Issue Health 10%
50
License 10%
100
Description 5%
100

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