SkillsAdd

smithery/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.

Installation

$ npx skills add smithery/sd0xdev --skill git-investigate
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

investigate-without-getting-made Similar name
useosint/skills

>- Investigator OPSEC — threat-model who might notice you, control your attribution surface acr…

58.1K installs
investigate-first Similar name
juliusbrussee/caveman

Diagnose ambiguous failures before editing. Use for unknown causes, intermittent behavior, perf…

38.8K installs
investigate-anything Similar name
useosint/skills

>- Start-here router and tradecraft baseline for any investigation into a person, company, doma…

1.6K installs
investigate Similar name
ghaida/intent

Guide and conduct user research — from planning through synthesis. Interview scripts, survey de…

1.6K installs
k6-cloud-investigate-test Similar name
grafana/skills

Investigate a Grafana Cloud k6 test — describe the script, list run history, identify pass/fail…

1.3K installs
investigate Similar name
cyrusagents/cyrus

Research the codebase to answer questions. Search for relevant files, gather context, and provi…

36 installs

Also in this package

Other skills from smithery/sd0xdev.

npx skills add smithery/sd0xdev
tech-spec 0 repo-intake 0 issue-analyze 0 feature-verify 0 feasibility-study 0 create-request 0 codex-cli-review 0 codex-brainstorm 0 code-explore 0

Browse all from smithery/sd0xdev

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsBash(git:*), Read, Grep, Glob, Agent

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,533 B
  • docs SUMMARY.md 138 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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