# Memorix Git Memory

> Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.

- Skill: `avids2/memorix-git-memory` (Agent Skill)
- Install (CLI): `npx skillmds@latest add avids2/memorix-git-memory`
- Raw SKILL.md: https://api.skillmd.com/api/skills/avids2/memorix-git-memory/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: avids2 (https://skillmd.com/u/avids2)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/avids2/memorix-git-memory

---


# Memorix Git Memory

Use Git Memory for repository evidence. Use reasoning memory for intent.

## Tool Router

| 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` |

## Retrieval Rules

- Prefer Git Memory for "what changed", "when did this ship", "which files were touched", and "which commit introduced this".
- Prefer reasoning memory for "why did we choose this", "what alternatives existed", and "what risk did we accept".
- Cross-link important decisions with `relatedCommits` when storing reasoning.
- Do not force-ingest noisy commits unless the skipped commit is genuinely important evidence.