Search codebase and git history for keywords. Use when investigating code changes, finding where features were added, or tracking down when bugs were introduced.
Install with the open skills CLI (global, non-interactive — available in every Claude Code session):
npx skills add FastLED/FastLED --skill "git-historian" -g -a claude-code -yOr manually — copy the SKILL.md below into:
~/.claude/skills/git-historian-fastled-2/SKILL.md---
name: git-historian
description: Search codebase and git history for keywords. Use when investigating code changes, finding where features were added, or tracking down when bugs were introduced.
argument-hint: <keyword1> [keyword2] [...] [--paths dir1 dir2]
---
Search the codebase and git history for the specified keywords.
Arguments: $ARGUMENTS
This command searches both:
1. Working tree files (current code state)
2. 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.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes