dev.git

Compose single git queries to trace file history and compare branches.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/lburgazzoli/claude-plugins --skill dev-git
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev.git
Source: https://github.com/lburgazzoli/claude-plugins/tree/main/skills/dev.git
Command: npx skills add https://github.com/lburgazzoli/claude-plugins --skill dev-git

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explains how to explore git history, trace changes, and analyze branches by composing single, non-trivial git queries instead of chaining multiple commands.

Core Features & Use Cases

  • Compose and optimize git queries that replace multiple commands (log, diff, blame) with one actionable command.
  • Guide for tracing file history with --follow, analyzing branch differences, and extracting concise change summaries.
  • Real-world scenarios include auditing changes, validating fixes across branches, and locating when a symbol or file first appeared.

Quick Start

Ask it to compose a single git query that traces changes to a target file or symbol across branches.

Frequently Asked Questions about dev.git

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

FAQPage Schema
How do I trace file history across branches with a single git query?▼

You can trace file history across branches by composing a single git query using the --follow flag to track renames and --stat to summarize changes, replacing the need to chain multiple log and diff commands.

What is the best way to compare branch differences in git without running multiple commands?▼

Comparing branch differences is best done by composing one optimized git query that analyzes logs and diffs together, extracting concise change summaries to audit differences efficiently across commits.

Can I find when a symbol or file first appeared in git history using one command?▼

Yes, you can locate when a symbol or file first appeared by composing a single non-trivial git query that uses grep and log parameters to search through commit history and output machine-parseable results.

How do I get concise machine-parseable output from git log for auditing changes?▼

To get concise machine-parseable output for auditing changes, compose a single git query that enforces formatting and efficiency rules, utilizing flags like --follow and --stat to produce targeted summaries instead of verbose logs.

Does composing a single git query work for validating fixes across multiple branches?▼

Composing a single git query works for validating fixes across branches by combining branch comparison logic and history tracing into one actionable command, ensuring you extract concise change summaries without multiple executions.