memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
$ npx -y skills add AVIDS2/memorix --skill memorix-git-memory --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/memorix-git-memoryContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
name: memorix-git-memory description: Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
Use Git Memory for repository evidence. Use reasoning memory for intent.
| Situation | Prefer | CLI fallback | |---|---|---| | Search what changed | `memorix_search` with a change-focused query | `memorix memory search --query "what changed <topic>"` | | Inspect a git-backed memory | `memorix_detail` | `memorix memory detail --id <id>` | | Ingest current commit manually | CLI | `memorix ingest commit` | | Ingest a specific commit | CLI | `memorix ingest commit --ref <ref>` | | Backfill recent history | CLI | `memorix ingest log --count 20` | | Install post-commit ingestion | CLI | `memorix git-hook --force` |
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
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 a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether session_start is useful.
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.