Imported from tomevault-io/tomes (sd0xdev--sd0x-dev-flow/skills/git-investigate/SKILL.md). Install upstream with npx skills add tomevault-io/tomes --skill git-investigate. Copyright stays with the author.

name: git-investigate description: 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. Use when this capability is needed. metadata: author: sd0xdev

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

Common Patterns

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

Converted and distributed by TomeVault — claim your Tome and manage your conversions.