skills.rest
FastLED
FastLEDOFFICIAL
Explore all skills by this author →
WebsiteGitHub

git-historian

Search codebase and git history for keywords with optional path filtering.

7.5k|1.8k|Updated Nov 10, 2013
Search Tags:#git#codebase#search#auditing#history#keywords#tracking
One-click install
npx skills add https://github.com/FastLED/FastLED --skill git-historian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-historian
Source: https://github.com/FastLED/FastLED/tree/main/.claude/skills/git-historian
Command: npx skills add https://github.com/FastLED/FastLED --skill git-historian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Search codebase and git history for keywords. Use when investigating code changes, finding where features were added, or tracking down when bugs were introduced.

Core Features & Use Cases

  • Search both working tree files (current code state) and git history for specified keywords.
  • Extract keywords from the arguments and route them to the git_historian MCP tool, with optional --paths filtering.
  • Present results with clear, contextual information about current locations and historical diffs.

Quick Start

Run the git-historian with your keywords to search both the working tree and recent git history, optionally specifying --paths to narrow the scope.

Frequently Asked Questions about git-historian

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search git history for a specific keyword in my codebase?▼

To search git history for a specific keyword, you can extract the keyword and route it to the git historian tool to locate current working tree files and historical diffs where the term appears.

What is the best way to trace when a feature was introduced in git?▼

Tracing feature introductions in git involves analyzing historical diffs for related keywords to pinpoint the exact revision where the code changes occurred.

Can I scope git history searches to specific file paths?▼

Yes, you can scope git history searches to specific file paths by applying optional path filtering arguments to narrow the code exploration results.

How does auditing codebase changes across git revisions work?▼

Auditing codebase changes across git revisions works by extracting keywords from your query and matching them against historical diffs to track modifications over time.

How do I debug when a bug was introduced using git history?▼

Debugging when a bug was introduced using git history requires searching past revisions for relevant keywords to identify the specific commit that introduced the erroneous code.

Does git historian search both the current working tree and past commits?▼

Yes, git historian searches both the current working tree files and past git commit history to provide clear contextual information about keyword locations and historical diffs.

Related Skills

Explore More Software Engineering Skills→
kaosnyrbkaosnyrb
12

commit

Stage and commit Git changes with a diff-derived message.

Community
Intermediate
a29paula29paul
1

gstack-openclaw-investigate

Enforce root cause investigation before bug fixes in software debugging workflows.

Community
Advanced
nguyenphpnguyenphp
41

lint-and-validate

Run linters, type checkers, and security audits across Node.js and Python projects.

Community
Intermediate
seedprodseedprod
93

session-logs

Search and analyze JSONL conversation logs using jq and ripgrep.

Community
Intermediate