memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether session_start is useful.
$ npx -y skills add AVIDS2/memorix --skill memorix-sessions --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/memorix-sessionsContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether session_start is useful.
name: memorix-sessions description: Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether session_start is useful.
`memorix_session_start` is optional. Use it when session semantics help; do not make memory-only work heavier than needed.
| Situation | Prefer | CLI fallback | |---|---|---| | Resume a prior long-running task | `memorix_session_start` | `memorix session start --agent <name>` | | HTTP control plane needs project binding | `memorix_session_start` with `projectRoot` | `memorix session start --projectRoot <absolute-path>` | | Need recent handoff/session summaries | `memorix_session_context` | `memorix session context` | | End a real working session | `memorix_session_end` | `memorix session end --sessionId <id> --summary "<summary>"` | | Need explicit subagent coordination identity | `memorix_session_start` with `joinTeam: true` | `memorix session start --joinTeam --agentType <agent>` |
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 the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
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 Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.