memorix-memory

Featured

Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.

AI & Automation 583 stars 45 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 91/100

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

Skill Content

# Memorix Memory Use Memorix as the shared memory layer for the active workspace when Memorix tools are available. ## Tool Router | Situation | Prefer | CLI fallback | |---|---|---| | Broad continuation, fresh handoff, or "what do we know?" | `memorix_project_context` with the user's task | `memorix context --task "<topic>"` | | Need structured refs/freshness for code-bound memories | `memorix_context_pack` | `memorix codegraph context-pack --task "<topic>"` | | Explicit memory graph question | `memorix_graph_context` | `memorix memory graph-context --query "<topic>"` | | Specific past decision, bug, file, or change | `memorix_search` | `memorix memory search --query "<topic>"` | | Need the full source for a search hit | `memorix_detail` | `memorix memory detail --id <id>` | | Need the sequence around one memory | `memorix_timeline` | `memorix memory timeline --id <id>` | | Learned reusable project knowledge | `memorix_store` | `memorix memory store --type <type> --entity <name> --title "<title>" "<text>"` | | Task or bug is complete/outdated | `memorix_resolve` | `memorix memory resolve --ids <ids>` | ## Search Rules - Search before broad continuation work, before changing unfamiliar code, or when the user asks about prior work. - For a fresh coding session, use `memorix_project_context` with the user's actual task before ad-hoc file reads or dev-log reads. Memorix will choose a task-lensed brief. - Fetch detail before relying on a specific memory. - Treat memory as bac...

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