git-historian
SkillSearchLets your agent search a codebase and its git history to find keywords and trace when changes or bugs appeared.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the git-historian skill
About this capability
Search codebase and git history for keywords. Use when investigating code changes, finding where features were added, or tracking down when bugs were introduced.
What this skill tells your AI
The instructions your AI receives, as published by fastled/fastled in .claude/skills/git-historian/SKILL.md and read by ahel’s review.
Search the codebase and git history for the specified keywords.
Arguments: $ARGUMENTS
This command searches both:
- Working tree files (current code state)
- Git history (last 10 commits' diffs)
Usage examples:
/git-historian LED strip/git-historian "error handling" config/git-historian memory leak --paths src tests
Extract the keywords from the arguments and call the git_historian MCP tool with those keywords.
If --paths is specified, extract the paths that follow it and pass them as the paths parameter.
Otherwise, pass an empty paths array to search the entire repository.
Present the results in a clear, readable format showing both current code locations and historical context.
Signals
- GitHub stars
- 7k
- Forks
- 2k
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
git-historian- Source
- github.com/fastled/fastled