agentleFS
Sign inStart free
sd0xdevsd0xdev/sd0x-harness/skills/git-investigate/SKILL.md

git-investigate

Skill192 starsChanged 37 days agoMITView on GitHub

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.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Create a free account to mount
Files
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

QuestionMethod
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

PatternSymptomRoot Cause
Type removedEnum value deletedAssumed no longer needed
Condition simplifiedIf conditions reducedMissed during refactoring
RenamePartially unchangedIncomplete search-and-replace
Boundary ignoredOnly handles main flowEdge 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free