Git Memory Search

Search Git History with git-memory

When to Use

• User asks why something was built a certain way
• User is about to edit a module and needs context
• User reports a bug that may have been fixed before
• User asks about a past decision, refactor, or migration
• You need to understand the evolution of a component

Workflow

1. Identify the topic/component from the user's question
2. Call search_git_history(query, limit=8)
3. If results are few, also call bug_fix_history(component)
4. If the user mentions a specific file, call commits_touching_file(filename)
5. Synthesise results into a clear narrative for the user

Checklist

- [ ] Called search_git_history with a descriptive query
- [ ] Applied category filter if user is looking for a specific type (fix, feat, security)
- [ ] Checked commits_touching_file if a specific file is involved
- [ ] Included commit hashes in the answer so user can run git show
- [ ] Noted the date range of relevant commits

Tool Details

searchgithistory

search_git_history(
    query="payment state machine race condition",
    limit=8,
    category="fix"   // optional: fix | feat | security | refactor | migration | arch | perf
)

Returns commits ranked by cosine similarity (0–1 score). Score > 0.7 = highly relevant.

commitstouchingfile

commits_touching_file(
    filename="PaymentService.ts",   // partial match supported
    limit=10
)

Returns all commits that modified the file, newest first, enriched with ChromaDB category.

bugfixhistory

bug_fix_history(
    component="payments",
    limit=8,
    include_security=true
)

Returns fix/bug/hotfix/security commits for the component, ranked by relevance.

architecture_decisions

architecture_decisions(
    topic="state machine order transitions",
    limit=5
)

Returns refactor/migration/arch commits. Useful for "why is this designed this way?" questions.

Example

User: "Why does the payment flow go through a state machine?"

1. search_git_history("payment state machine order transitions", limit=5)
   → [32c3389f] fix(payments): route 3DS callback through transitionStatus
     score=0.633 — "Replace direct repository updates with transitionStatus
     calls to enforce the allowed-transitions guard"

2. commits_touching_file("PaymentService.ts", limit=5)
   → [32c3389f] fix(payments): route 3DS callback...
   → [599d531b] feat: add Garanti 3DS payments...

3. Answer: "The state machine was introduced in commit 32c3389f to prevent
   race conditions on 3DS callbacks."

Source & license

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

• Author: gunesbizim
• Source: gunesbizim/agent-smith
• License: MIT

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