ReddRadar
Agent skill
git-investigate
Code investigation knowledge base. Covers code history tracking, issue introduction analysis, root cause diagnosis.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/git-investigate
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 |
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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?