Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
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…
Install Basemind Git History
$ npx skills add Goldziher/basemind --skill basemind-git-history -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Goldziher/basemind basemind-git-history --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Goldziher/basemind.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/basemind-git-history .claude/skills/basemind-git-history && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "basemind-git-history" agent skill from https://github.com/Goldziher/basemind/tree/main/skills/basemind-git-history into .claude/skills/basemind-git-history/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "basemind-git-history", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Goldziher/basemind/tree/main/skills/basemind-git-historyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Goldziher/basemind --skill basemind-git-history -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Goldziher/basemind basemind-git-history --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Goldziher/basemind.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/basemind-git-history .agents/skills/basemind-git-history && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "basemind-git-history" agent skill from https://github.com/Goldziher/basemind/tree/main/skills/basemind-git-history into .agents/skills/basemind-git-history/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "basemind-git-history", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Goldziher/basemind --skill basemind-git-history -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Goldziher/basemind basemind-git-history --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Goldziher/basemind.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/basemind-git-history .cursor/skills/basemind-git-history && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "basemind-git-history" agent skill from https://github.com/Goldziher/basemind/tree/main/skills/basemind-git-history into .cursor/skills/basemind-git-history/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "basemind-git-history", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Goldziher/basemind.git --path skills/basemind-git-history--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Goldziher/basemind --skill basemind-git-history -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Goldziher/basemind basemind-git-history --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Goldziher/basemind.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/basemind-git-history .gemini/skills/basemind-git-history && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "basemind-git-history" agent skill from https://github.com/Goldziher/basemind/tree/main/skills/basemind-git-history into .gemini/skills/basemind-git-history/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "basemind-git-history", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Goldziher/basemind basemind-git-historyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Goldziher/basemind --skill basemind-git-history -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Goldziher/basemind.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/basemind-git-history .github/skills/basemind-git-history && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "basemind-git-history" agent skill from https://github.com/Goldziher/basemind/tree/main/skills/basemind-git-history into .github/skills/basemind-git-history/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "basemind-git-history", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Goldziher/basemind --skill basemind-git-history -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Goldziher/basemind basemind-git-history --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Goldziher/basemind.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/basemind-git-history .opencode/skills/basemind-git-history && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "basemind-git-history" agent skill from https://github.com/Goldziher/basemind/tree/main/skills/basemind-git-history into .opencode/skills/basemind-git-history/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "basemind-git-history", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
basemind-git-history- GitHub stars
- 108
- Token cost
- ~851 tokens
- SKILL.md length
- 350 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
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…
- Tasks that involve Git workflow
- SKILL.md covers Tool routing, Examples and Notes
- Calls git
What it does
Basemind Git History is an agent skill from Goldziher/basemind. 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".
Its SKILL.md is about 850 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Git workflow. It works with Git. The repository describes itself as: Full AI context and content layer for coding agents over one MCP server — tree-sitter code-map, document RAG, shared memory, multi-agent comms, web crawl, git history + blame… The licence is MIT.
When your agent uses it
- Tasks that involve Git workflow
Example prompts
- “s history over time. Reach for it whenever the user asks”
- “who last touched this”
- “when did this symbol change”
- “/basemind-git-history”
What it can do on your machine
Read from SKILL.md and the folder at commit 2f6da31. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Basemind Git History loads about 851 tokens when it runs. Until then it costs about 101 tokens; SKILL.md has 350 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Goldziher/basemind at commit 2f6da31, republished under its MIT licence (© Goldziher). 350 words, ~851 tokens.
Download SKILL.mdSave it as
.claude/skills/basemind-git-history/SKILL.md (or your agent's skills folder).- name
- basemind-git-history
- 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".
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 |
| "Path-filtered commit log?" | 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 "…" |
Show full SKILL.md (89 more words)Show less
Examples
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 serveto be running inside a git repository. Outside a git repo they return a clear error. - History queries are indexed:
gitmodetouchingand 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. Lists are capped
(
limit, default 100, max 1000).
For code structure see basemind-code-search; for document RAG and semantic search see
basemind-documents; for agent coordination see basemind-comms.
© Goldziher, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/basemind-git-history of Goldziher/basemind.
Open the folder on GitHubat commit 2f6da31
Compare with similar skills
Basemind Git History next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Basemind Git History this skillGoldziher/basemind | 108 | — | ~851 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 11k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Migrate Internal Package into GhostTryGhost/Ghost | 56k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Create Pull Requestcline/cline | 70k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Code Design Rationale Investigator
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Migrate Internal Package into Ghost
TryGhost/Ghost
Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
Git Merge Conflict Resolver
tailcallhq/forgecode
Resolves Git merge conflicts with a plan-first workflow that keeps both sides' intent, regenerates lock files and backs up deleted-but-modified files.
More from Goldziher/basemind
All 10 skills in this repoBasemind Usage Stats
Goldziher/basemind
Shows a markdown dashboard of basemind activity in the session: tool call counts, top operations and estimated tokens saved against a grep and Read baseline.
Basemind Code Context
Goldziher/basemind
Answers structural questions about a repository, such as where a symbol is defined, what calls it and what changed recently, through the basemind MCP server.
Basemind Index Scan
Goldziher/basemind
Builds or refreshes the basemind code index from the command line, for when basemind reports no index or its MCP server is not running.
basemind CLI Codebase Navigator
Goldziher/basemind
Drives the basemind code-intelligence tool from the command line for symbol search, callers, git history and blame, document search and web crawling, sharing its cache with the MCP server.
Basemind Code Search
Goldziher/basemind
Answers where code is defined, who calls it and what shape a file has from a pre-built index, returning paths and line numbers instead of file contents.
Basemind Doctor
Goldziher/basemind
Diagnose and recover basemind when it isn't working — MCP tools missing or erroring, "no index" / "no indexed files", empty results that shouldn't be empty, or the MCP server seems dead.
Related
Works with
Categories
Questions about Basemind Git History
What does Basemind Git History do?
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…. Basemind Git History is an agent skill from Goldziher/basemind. 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.
When should I use Basemind Git History?
Basemind Git History fits situations like: tasks that involve Git workflow.
How do I install Basemind Git History in Claude Code?
Run `npx skills add Goldziher/basemind --skill basemind-git-history -a claude-code`. Or copy the skill folder (skills/basemind-git-history in Goldziher/basemind) into .claude/skills/basemind-git-history in your project. Claude Code loads it when a task matches its description.
How do I install Basemind Git History in Codex?
Run `npx skills add Goldziher/basemind --skill basemind-git-history -a codex`. Or copy the skill folder (skills/basemind-git-history in Goldziher/basemind) into .agents/skills/basemind-git-history in your project. Codex loads it when a task matches its description.
Can I use Basemind Git History in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Goldziher/basemind --skill basemind-git-history -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/basemind-git-history, .gemini/skills/basemind-git-history, .github/skills/basemind-git-history and .opencode/skills/basemind-git-history in your project.
What does Basemind Git History need to run?
Going by SKILL.md and its folder, Basemind Git History needs the command-line tools its instructions call (git).
Does Basemind Git History access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Basemind Git History safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Basemind Git History use?
Basemind Git History is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Basemind Git History use?
About 851 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Basemind Git History?
Skills that share tags, products or a category with Basemind Git History: Finishing a Development Branch (obra/superpowers, 297k stars), Code Design Rationale Investigator (cursor/plugins, 11k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Migrate Internal Package into Ghost (TryGhost/Ghost, 56k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Basemind Git History?
Goldziher (a GitHub user) maintains it in Goldziher/basemind, which has 108 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 10, 2026.
Source: Goldziher/basemind on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.