Stats
Actions
Tags
From majestic-engineer
Analyzes git history using git log, blame, shortlog to trace code evolution, map contributors, and identify commit patterns for repo archaeology.
How this skill is triggered — by the user, by Claude, or both
Slash command
/majestic-engineer:git-researcherThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Audience:** Developers needing to understand how and why code evolved to its current state.
Audience: Developers needing to understand how and why code evolved to its current state.
Goal: Analyze git history to trace code evolution, identify contributors, and extract patterns that inform current development decisions.
| Purpose | Command |
|---|---|
| File history (recent) | git log --follow --oneline -20 <file> |
| Code origin tracing | git blame -w -C -C -C <file> |
| Pattern search in commits | git log --grep="<keyword>" |
| Contributor mapping | git shortlog -sn -- <path> |
| Code introduction/removal | git log -S"<pattern>" --oneline |
| Co-changed files | git log --name-only --oneline -- <file> |
| Dimension | What to Look For |
|---|---|
| Change context | Feature additions vs bug fixes vs refactoring |
| Change frequency | Rapid iteration vs stable periods |
| File coupling | Files that always change together |
| Pattern evolution | How coding practices changed over time |
## Timeline of File Evolution
- [Date]: [Purpose of change]
## Key Contributors and Domains
- [Contributor]: [Areas of expertise]
## Historical Issues and Fixes
- [Pattern of problems and resolutions]
## Change Patterns
- [Recurring themes, refactoring cycles, architecture evolution]
npx claudepluginhub majesticlabs-dev/majestic-marketplace --plugin majestic-engineerAnalyzes git history to find code hotspots, temporal coupling between files, contributor knowledge distribution, and bus factor risks. Useful for queries on code ownership, frequent changes, or evolution.
Traces evolution of files or functions through git history to identify structural commits adding complexity. Helps assess necessity for refactoring.
Traces git history to find when and why code changed, who wrote it, and root cause of bugs. Use for code archaeology, git blame, and change tracking.