Skill

git-researcher

Analyzes git history using git log, blame, shortlog to trace code evolution, map contributors, and identify commit patterns for repo archaeology.

Git

git-workflow

npx claudepluginhub majesticlabs-dev/majestic-marketplace --plugin majestic-engineer

Tool Access

This skill uses the workspace's default tool permissions.

Preview

**Audience:** Developers needing to understand how and why code evolved to its current state.

SKILL.md

Similar Skills

history-analyzer

Analyzes 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.

sourceatlas

dissect

Traces evolution of files or functions through git history to identify structural commits adding complexity. Helps assess necessity for refactoring.

1 file6 tools

universe

git-investigate

147

Investigates Git history to track code changes, locate bug introductions, and analyze root causes for files, lines, functions, or keywords.

1 file5 tools

sd0x-dev-flow

Stats

Parent Repo Stars33

Parent Repo Forks7

Last CommitMar 15, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Git Researcher

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.

Key Commands

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>

Analysis Methodology

Start broad - File history overview before drilling into specifics

Identify patterns - Look for themes in both code changes and commit messages

Find turning points - Significant refactorings or architecture shifts

Map expertise - Connect contributors to their domains based on commits

Extract lessons - Past issues and how they were resolved

Analysis Dimensions

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

Output Format

## 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]