How do I install the Git Investigate skill?

Run npx skillmds@latest add sd0xdev/git-investigate in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Git Investigate safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Investigate?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Investigate free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Investigate?

sd0xdev (@sd0xdev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Investigate by sd0xdev — Agent Skill

Name: Git Investigate
Author: sd0xdev

Git Investigate

Git history investigation. Use when: tracking code changes, finding where bugs were introduced, root cause analysis. Not for: code exploration (use code-explore), issue analysis (use issue-analyze). Output: history trace + root cause report.

sd0xdev Updated Sep 17, 2026

File contents

Git Investigate Skill

Trigger

Keywords: code history, git blame, track changes, who wrote this, when was it changed, root cause, code archaeology

When NOT to Use

Code review (use codex-review)
Feature development (use feature-dev)
Just want to read code (use Read directly)

Command

/git-investigate src/service/xxx.ts:123      # Specific line
/git-investigate processToken                 # Function name
/git-investigate "error message"              # Keyword

Workflow

Locate code -> git blame -> find commit -> trace history -> analyze changes -> report

Investigation Framework

Question	Method
Who wrote it?	`git blame`
When was it changed?	`git log --follow`
Why was it changed?	commit message + PR
What was missed?	`git diff` compare original vs problematic version

Common Patterns

Pattern	Symptom	Root Cause
Type removed	Enum value deleted	Assumed no longer needed
Condition simplified	If conditions reduced	Missed during refactoring
Rename	Partially unchanged	Incomplete search-and-replace
Boundary ignored	Only handles main flow	Edge cases not considered

Output

## Git Investigation Report
- **Target**: <file/feature>
- **Timeline**: <commit range>
- **Root cause**: <analysis>
- **Introduced by**: <commit hash + author>

Verification

Report includes: investigation target, author info, timeline, original vs problematic code
Root cause has clear analysis
Fix recommendation is specific and actionable

References

references/commands.md - Git command reference + report template

Examples

Input: Who changed this line of code?
Action: git blame -> find commit -> trace PR -> output report

Input: When was this bug introduced?
Action: git log -p -S -> locate introduction point -> analyze cause -> output report

---name: git-investigatedescription: Git history investigation. Use when: tracking code changes, finding where bugs were introduced, root cause analysis. Not for: code exploration (use code-explore), issue analysis (use issue-analyze). Output: history trace + root cause report.---# Git Investigate Skill## Trigger- Keywords: code history, git blame, track changes, who wrote this, when was it changed, root cause, code archaeology## When NOT to Use- Code review (use codex-review)- Feature development (use feature-dev)- Just want to read code (use Read directly)## Command```bash/git-investigate src/service/xxx.ts:123 # Specific line/git-investigate processToken # Function name/git-investigate "error message" # Keyword```## Workflow```Locate code -> git blame -> find commit -> trace history -> analyze changes -> report```## Investigation Framework| Question | Method || ------------------ | ----------------------------- || Who wrote it? | `git blame` || When was it changed?| `git log --follow` || Why was it changed?| commit message + PR || What was missed? | `git diff` compare original vs problematic version |## Common Patterns| Pattern | Symptom | Root Cause || ------------------ | -------------------- | ----------------------------- || Type removed | Enum value deleted | Assumed no longer needed || Condition simplified| If conditions reduced| Missed during refactoring || Rename | Partially unchanged | Incomplete search-and-replace || Boundary ignored | Only handles main flow| Edge cases not considered |## Output```markdown## Git Investigation Report- **Target**: <file/feature>- **Timeline**: <commit range>- **Root cause**: <analysis>- **Introduced by**: <commit hash + author>```## Verification- Report includes: investigation target, author info, timeline, original vs problematic code- Root cause has clear analysis- Fix recommendation is specific and actionable## References- `references/commands.md` - Git command reference + report template## Examples```Input: Who changed this line of code?Action: git blame -> find commit -> trace PR -> output report``````Input: When was this bug introduced?Action: git log -p -S -> locate introduction point -> analyze cause -> output report```

Frequently asked questions