git-forensics

What problem does it solve?

Git forensics answers questions that code alone cannot: who last touched a piece of logic, when a change occurred, and why it happened. The history doesn't just record what changed — it records who changed it, when, and (if commit messages are good) why they changed it.

Core Features & Use Cases

• History discovery: use commands like git log, git blame, and git show to trace changes, authors, and context across commits.
• Regression and change tracing: leverage git bisect, git log with -S/-G, and git blame for pinpointing when behavior changed.
• Recovery, auditing, and ref movement: use git reflog to recover lost work, track ref updates, and understand renames/merges over time.

Quick Start

Start by running basic investigations with git blame and git log to trace changes in your repository.