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 durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
$ npx -y skills add AVIDS2/memorix --skill memorix-mini-skills --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/memorix-mini-skillsContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
name: memorix-mini-skills description: Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
Promote memories into mini-skills only when they are reusable instructions, not just historical notes.
The standard setup uses the `lite` MCP profile. `memorix_skills` and `memorix_promote` are full-profile tools, so use the CLI fallback unless the current server was explicitly started with `MEMORIX_MODE=full` or `--mode full`. Do not probe hidden MCP tools repeatedly.
| Situation | Prefer | CLI fallback | |---|---|---| | Preview/discover existing project skills | `memorix_skills` action `list` | `memorix skills list` | | Generate skills from memory patterns | `memorix_skills` action `generate` | `memorix skills generate` | | Write generated skills to an agent | `memorix_skills` action `generate`, `write: true` | `memorix skills generate --write --target codex` | | Promote selected memories permanently | `memorix_promote` action `promote` | `memorix memory promote --ids 42,43` | | List/delete promoted mini-skills | `memorix_promote` | `memorix memory promote --action list|delete` |
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 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.