Search codebase and git history for keywords. Use when investigating code changes, finding where features were added, or tracking down when bugs were introduced.
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add majiayu000/claude-skill-registry --skill git-historian --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Git Historian?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/majiayu000-git-historian)More formats (shields.io, HTML) on the badges page.
---
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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
