AgentStack
SKILL verified MIT Self-run

Git Memory Index

skill-gunesbizim-agent-smith-git-memory-index · by gunesbizim

Use when the user wants to index a repository into git-memory, start using git-memory on a new project, or re-index after significant history. Examples: \"index the lokumcu repo\", \"set up git memory for this project\", \"re-index everything\

No reviews yet
0 installs
15 views
0.0% view→install

Install

$ agentstack add skill-gunesbizim-agent-smith-git-memory-index

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Git Memory Index? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Index a Repository with git-memory

When to Use

  • Starting git-memory on a new repository for the first time
  • After a major history rewrite or large batch of commits
  • User explicitly asks to (re-)index a project
  • Setting up git-memory for a team member's repo

Workflow

1. Confirm the repo path with the user (default: current directory)
2. Run a dry-run first to show what will be indexed
3. Ask if the user wants to limit commit count (useful for very large repos)
4. Run the real index
5. Run git-memory install to register the MCP server

Checklist

- [ ] Confirmed repo path
- [ ] Ran dry-run to preview commit count and filter results
- [ ] Agreed on --limit if repo has >1000 commits
- [ ] Completed indexing with 0 errors
- [ ] MCP server registered in .claude.json
- [ ] Reminded user to restart Claude Code

Commands

Dry run (preview what will be indexed)

git-memory index \
  --repo-path /path/to/repo \
  --user-id my-repo-name \
  --dry-run

Full index

git-memory index \
  --repo-path /path/to/repo \
  --user-id my-repo-name
# Add --limit 500 for large repos (indexes 500 newest commits)

Install Claude Code plugin

git-memory install \
  --repo-path /path/to/repo \
  --user-id my-repo-name

Or from within the repo directory

cd /path/to/repo
git-memory index --user-id my-repo-name
git-memory install --user-id my-repo-name

Expected Output

Found 42 commits to evaluate
Done. {"total_evaluated":42,"stored":39,"skipped_irrelevant":3,"skipped_duplicate":0,"errors":0}

── Indexing Summary ─────────────────────────────
  total_evaluated           42
  stored                    39
  skipped_irrelevant        3
  skipped_duplicate         0
  errors                    0

Notes

  • Skipped irrelevant: Commits with no signal keywords (e.g. "k", "wip", "merge") are skipped by design. This keeps the index signal-rich.
  • Deduplication: Safe to run multiple times — ChromaDB deduplicates by commit hash.
  • Large repos: For repos with >10k commits, use --limit 1000 to index the most recent 1000.
  • user-id: Use a distinct ID per repo so multiple repos can coexist in the same index.
  • Embed providers: Defaults to Ollama (nomic-embed-text). Set GITMEMORYEMBED_PROVIDER=openai for OpenAI or =fastembed for fully local (no Ollama needed).

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.