git-advanced

Name: git-advanced
Availability: InStock
Author: alangeb

Perform Git bisecting, cherry-picking, and log analysis operations locally.

Updated Jun 22, 2026

Search Tags:#git #history #cherry-pick #stash #bisect #log #blame

Ready to run

npx skills add https://github.com/alangeb/tau --skill git-advanced-alangeb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-advanced
Source: https://github.com/alangeb/tau/tree/main/src/skills/git-advanced
Command: npx skills add https://github.com/alangeb/tau --skill git-advanced-alangeb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill simplifies complex Git operations like bisecting history, cherry-picking commits, and performing deep log analysis, which are often error-prone when done manually.

Core Features & Use Cases

Advanced History Analysis: Quickly filter logs by author, content, or time range to identify the source of regressions.
Automated Bisecting: Streamlines the process of finding the specific commit that introduced a bug.
Safe Cherry-Picking: Provides a structured workflow for porting specific changes between branches while maintaining repository integrity.

Quick Start

Ask the agent to perform a git log analysis on the current directory to identify recent changes.

Frequently Asked Questions about git-advanced

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

FAQPage Schema

How do I find the specific commit that introduced a bug using git bisect?▼

Git bisect automates bug investigation by binary searching commit history to pinpoint the exact regression source. This skill streamlines the bisecting workflow within local repositories to identify the offending commit efficiently.

What is the best way to cherry-pick commits between branches without breaking repository history?▼

Cherry-picking ports specific changes between branches while maintaining repository integrity. This skill provides a structured workflow for safe cherry-picking operations to ensure history remains clean during branch porting.

How do I analyze git log history to filter commits by author or time range?▼

Git log analysis filters commit history by author, content, or time range to audit changes. This skill extracts commit metadata from local development repositories to identify recent regressions and track modifications.

Can I use this skill to investigate regressions in any local git repository?▼

Yes, you can investigate regressions in any local git repository. This skill requires standard Git CLI tools and uses Python subprocess execution to manage repository state and extract commit metadata for analysis.

Why does git blame fail to show the full context of a recent code change?▼

Git blame shows the last modification per line but lacks broader historical context. Performing deep log analysis and history auditing with this skill reveals the full commit timeline and metadata surrounding the change.