Stats
Actions
Tags
From agent-smith
Use when the user wants to check what is indexed, how many commits are in memory, or whether git-memory is set up correctly. Examples: "is git memory set up?", "how many commits are indexed?", "check git memory status"
How this skill is triggered — by the user, by Claude, or both
Slash command
/agent-smith:git-memory-statusThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- User asks if git-memory is configured
1. Run status command to check ChromaDB commit count
2. Check if MCP server is configured in .claude.json
3. Check embed provider availability
4. Report findings and any gaps
- [ ] ChromaDB has > 0 commits indexed
- [ ] git-memory MCP server is in .claude.json
- [ ] user-id matches between index and MCP server config
- [ ] Embed provider is available (Ollama running / OPENAI_API_KEY set)
git-memory status --repo-path /path/to/repo
cat .claude.json | python3 -m json.tool | grep -A8 "git-memory"
curl -s http://localhost:11434/api/tags
── git-memory status ──────────────────────────
Repo : myproject
Chroma docs : 39 (this repo) / 39 (all repos)
Total commits : 42
Coverage : 93%
Embed provider: ollama
| Symptom | Fix |
|---|---|
0 commits indexed | Run git-memory index --repo-path . |
| MCP tools return errors | Check Ollama is running: ollama serve |
| Wrong user-id | Must match GIT_MEMORY_USER_ID in MCP config |
| Chroma path conflict | Ensure GIT_MEMORY_CHROMA_DIR points to chroma_commits/ |
| No LLM context (Layer 2) | Normal without Ollama — Layer 1 (ChromaDB) still works |
npx claudepluginhub gunesbizim/agent-smithGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.