skills.rest
latestaiagents
latestaiagentsOFFICIAL
Explore all skills by this author →
GitHub

git-history-detective

Investigate Git commit history with git blame, log, and bisect.

5|1|Updated Feb 4, 2026
Search Tags:#git#debugging#history#bisect#blame#commit log
One-click install
npx skills add https://github.com/latestaiagents/agent-skills --skill git-history-detective
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-history-detective
Source: https://github.com/latestaiagents/agent-skills/tree/main/plugins/developer-toolkit/skills/git/git-history-detective
Command: npx skills add https://github.com/latestaiagents/agent-skills --skill git-history-detective

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you navigate and understand the history of your Git repository, making it easier to find when changes were made, who made them, and why.

Core Features & Use Cases

  • Bug Tracking: Pinpoint the exact commit that introduced a bug using git bisect.
  • Code Evolution: Understand how a specific piece of code has changed over time with git blame and git log.
  • Author Identification: Quickly find out who last modified a particular line of code.
  • Use Case: When a feature suddenly stops working, use this skill to trace back through the commit history to find the exact change that caused the issue.

Quick Start

Use git blame to find out who last changed line 50 in the file src/utils.js.

Frequently Asked Questions about git-history-detective

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

FAQPage Schema
How do I find which commit introduced a bug in my git history?▼

To find a bug in your git history, use the git bisect process to binary search commits and pinpoint the exact regression. This identifies the specific change that caused the issue.

How can I see who changed a specific line of code using git blame?▼

Git blame identifies the author who last modified a specific line of code. It provides accountability by mapping changes in files like src/utils.js directly to their respective commit authors.

What is the best way to search a git log by commit message or content?▼

Searching the git log by message or content filters commit history to match specific text patterns. This reveals the reasons behind code evolution and uncovers when targeted modifications were made.

Can I trace when a feature stopped working by investigating the commit log?▼

Yes, investigating the commit log traces code evolution to find when a feature stopped working. You can review historical changes to understand how specific code segments altered over time.

Does git bisect work for tracking regressions across multiple files?▼

Yes, git bisect tracks regressions across the repository by navigating commit history. It systematically tests different states to isolate exactly when and where the bug was introduced.

Related Skills

Explore More Software Engineering Skills→
alangebalangeb

git-advanced

Perform Git bisecting, cherry-picking, and log analysis operations locally.

Community
Advanced
jobayerarmanjobayerarman

debugging

Diagnose and fix bugs in the Supplier Management System codebase.

Community
Intermediate
cxnaivecxnaive

requesting-code-review

Automate pre-commit code verification with static security analysis and regression checks.

Community
Advanced
HouseGarofaloHouseGarofalo
3

git-wizard-agent

Provides expert Git operations including bisect, worktree management, cherry-pick, and history rewriting.

Official
Advanced