basemind-git-history
/basemind-git-history
Bada historię repozytorium: ostatnie commity, blame dla linii i symboli, różnice między rewizjami i churn.
- Autor
- goldziher ↗
- Repozytorium
- basemind ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 1
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.
Co robi i kiedy
Bada historię repozytorium: ostatnie commity, blame dla linii i symboli, różnice między rewizjami i churn.
Wyzwalacze z opisu
Oryginalny opis (EN)
Explore git history without shelling out to git — recent commits, commits touching a path, per-line and per-symbol blame, structural diffs across revisions, churn ranking, and a symbol's history over time. Reach for it whenever the user asks "what changed recently", "who last touched this", "when did this symbol change", "what's the diff between these revs", or "where's the churn".
Jak działa
- Tool routing
- Examples
- Notes
Podgląd SKILL.md
---
description: Explore git history without shelling out to git — recent commits, commits touching a path, per-line and per-symbol blame, structural diffs across revisions, churn ranking, and a symbol's history over time. Reach for it whenever the user asks "what changed recently", "who last touched this", "when did this symbol change", "what's the diff between these revs", or "where's the churn".
name: basemind-git-history
license: MIT
metadata:
author: Goldziher
repository: https://github.com/Goldziher/basemind
---
<!--
AI-RULEZ :: GENERATED FILE — DO NOT EDIT
Content-Hash: blake3:a135da89c9a140974212c3d7338cd4f15bddce346228c8801727daee696d321b
Source-Hash: blake3:46d614160b39f13ea1f5ed2eee1206c23e7e16855f8d74854e50af5c5a241b49
Schema-Version: v1
-->
# basemind-git-history — git intelligence over the index
basemind indexes git history and resolves blame and diffs at **symbol** resolution, backed by a
`gix` history index. History queries return commits, authors, paths, and line/symbol attributions —
structured and capped — for a fraction of the cost of parsing `git log` / `git blame` output.
**basemind first, naked git fallback.** Prefer these tools over shelling out to `git log`,
`git blame`, or `git diff`. Drop to raw git only when no tool covers the question (e.g. staging,
rebasing, anything that mutates history).
## Tool routing
| Question | MCP tool | CLI |
|---|---|---|
| "What changed recently?" | `git { mode: "recent" }` | `basemind git recent [--limit N]` |
| "Which commits touched path P?" | `git { mode: "touching", path: P }` | `basemind git touching P` |
| "Commits whose changed paths match regex P?" | `git { mode: "by_path", pattern: P }` | `basemind git by-path P` |
| "When did symbol X last change?" | `git { mode: "symbol_history", path: F, name: X }` | `basemind git symbol-history F X` |
| "Who wrote this line?" | `git { mode: "blame", path: F }` | `basemind git blame F` |
| "Who wrote this symbol / when did its body change?" | `git { mode: "blame_symbol", path: F, name: X }` | `basemind git blame-symbol F X` |
| "Diff a file between revs?" | `git { mode: "diff", path: F, rev_old, rev_new }` | `basemind git diff F old new` |
| "What symbols did a branch add/remove?" | `git { mode: "diff_outline", path: F, rev }` | `basemind git diff-outline F [--rev]` |
| "Where's the churn?" | `git { mode: "churn" }` | `basemind git churn [--top-k N]` |
| "What's dirty in the working tree?" | `git { mode: "status" }` | `basemind git status` |
| "What's HEAD / branch / origin?" | `admin { mode: "repo" }` | `basemind admin repo` |
| "Full-text search commit messages + authors?" | `git { mode: "search", pattern: "…" }` | `basemind git search "…"` |
## Examples
```text
git { mode: "recent", limit: 5 }
→ 612df7e chore(release): v0.15.0
1779b99 fix(git-history,serve): address code-review findings
...
git { mode: "blame_symbol", path: "src/scanner.rs", name: "process_file" }
→ last touched by <author> in <commit> — body hash changed at HEAD~7
git { mode: "diff_outline", path: "src/mcp/tools.rs", rev: "HEAD~5" }
→ + search_history (function) - old_helper (function)
```
## Notes
- Git tools require `basemind serve` to be running **inside a git repository**. Outside a git repo
they return a clear error.
- History queries are indexed: `git` mode `touching` and friends resolve in tens of microseconds vs a
live walk. The index auto-builds on first use and is a fraction of the size of `.git`.
- All paths are repository-relative with forward-slash separators. `recent` and `search` return
at most 100 commits per page (`limit` default 20); `recent` is a recency window, so use `search`
to find an author or message arbitrarily far back. Page with `next_cursor` -> `cursor`; a moved
HEAD invalidates it (`cursor_invalidated`). A shallow clone sets `truncated`: absence is then
inconclusive.
For code structure see `basemind-code-search`; for document RAG and semantic search see
`basemind-documents`; for agent coordination see `basemind-comms`.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · goldziher/basemind | 100 | MIT |
| goldziher/basemind | 100 | MIT |
| goldziher/basemind | 84 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 0d6e6663593a (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 84basemind
Porusza się po dużych bazach kodu przez serwer MCP basemind: konspekty, wyszukiwanie symboli, odwołania i historię commitów. - 100basemind
Porusza się po dużych bazach kodu przez MCP: zarysy, wyszukiwanie symboli, wywołania, historię i diffy bez czytania plików. - 100system-history
Zbiera historię gita i pull requestów: wskazuje kruche obszary, ostatnie zmiany w plikach jako kandydatów do regresji i czyta diffy PR-ów. - 90git-analysis
Odpowiada na pytania z historii repozytorium: kto i kiedy zmienił kod, skąd wzięła się linia, gdzie weszła regresja. - 100commit-history
Wypisuje ostatnie commity git powiązane z sesjami agenta, opcjonalnie dla wybranej gałęzi lub repozytorium, żeby pokazać, co agent dostarczył i w jakim kontekście. - 100git-master
Wykonuje operacje git jak ekspert: atomowe commity z wykrywaniem stylu, rebase i squash oraz archeologia historii przez blame, bisect i pickaxe.