git-log

Query and interpret Git history via commits, authors, and branch topology.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/theslashdojo/dojo --skill git-log-theslashdojo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-log
Source: https://github.com/theslashdojo/dojo/tree/main/nodes/git/log
Command: npx skills add https://github.com/theslashdojo/dojo --skill git-log-theslashdojo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Quickly understand a project's history by inspecting commits, authors, and branch topology to answer who changed what and when.

Core Features & Use Cases

  • Filter commits by author, date, path, and message to locate relevant changes.
  • Visualize branch topology with graphs, decorates merges and divergences.
  • Use blame to attribute lines to contributors and bisect to identify bug-introducing commits.
  • Use case: auditing changes across multiple branches when preparing for a release or debugging.

Quick Start

Run git log --oneline --graph --all to view recent commits and branch topology.

Frequently Asked Questions about git-log

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I visualize branch topology and find recent commits in a git history?

To visualize git history and branch topology, run git log --oneline --graph --all to view recent commits, merges, and divergences across all branches in a structured graph format.

How do I filter git log to find commits by a specific author or date?

You can filter git log commits by author, date, path, and message to locate specific changes, allowing you to audit who modified what files and when across the project history.

What is the best way to locate the exact commit that introduced a bug across branches?

Use git bisect to locate the bug-introducing commit across branches, performing a deterministic binary search through the project history to isolate the exact change that caused the defect.

How does git blame attribute code changes to contributors?

Git blame attributes specific lines of code to contributors, showing which author last modified each line and the corresponding commit to trace the origin of changes.

Can I review changes across multiple branches when preparing for a release?

Yes, you can review changes across multiple branches by inspecting commits, authors, and branch topology, auditing the full git history to ensure release readiness and trace feature introductions.