git-guru

Guide Git workflows including rebase, worktrees, reflog recovery, and bisect debugging with validation checks and backups.

3|1|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/ProjAnvil/MindForge --skill git-guru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-guru
Source: https://github.com/ProjAnvil/MindForge/tree/main/skills/zh-cn/git-guru
Command: npx skills add https://github.com/ProjAnvil/MindForge --skill git-guru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git managers and teams struggle with messy commit histories, complex rebase workflows, and managing multiple worktrees, leading to lost context and risky changes.

Core Features & Use Cases

  • Interactive rebase, squash/fixup, and rewording of commits to create clean histories.
  • Git Worktree and multi-branch workflows to develop in isolation and safely merge later.
  • Reflog recovery, Bisect debugging, and advanced merge strategies to locate and fix issues efficiently.
  • Submodules, Git hooks, and Cherry-pick workflows to maintain modular and robust repositories.
  • Guidance on safe operations, backups, and guardrails to prevent data loss.

Quick Start

Run through a guided process to clean up a messy history and set up parallel worktrees for safe, concurrent development.

Frequently Asked Questions about git-guru

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

FAQPage Schema
How do I clean up a messy Git commit history with interactive rebase?

Clean up a messy Git commit history by using interactive rebase to squash, fixup, and reword commits. This process provides step-by-step commands and validation checks to streamline complex version control tasks safely.

What is the best way to manage multiple Git branches in isolation?

Manage multiple Git branches in isolation using Git worktree workflows. Worktrees allow concurrent development in separate directories without cloning, enabling safe isolation and later merging to streamline complex version control tasks.

How does Git bisect debugging work to locate the source of a bug?

Git bisect debugging works by performing a binary search through your commit history to locate the exact commit that introduced an issue. It guides you through checking out commits to efficiently locate and fix issues.

Can I recover lost commits after a hard reset using Git reflog?

Yes, you can recover lost commits after a hard reset using Git reflog. Reflog recovery tracks HEAD movements, providing backup workflows and validation checks to restore previous states and prevent data loss.

When do I need to use Git submodules and hooks in my repository?

Use Git submodules and hooks when maintaining modular and robust repositories. Submodules embed external repositories, while hooks automate validation checks and guardrails to maintain history hygiene and prevent data loss.

What are the limitations of cherry-pick workflows in Git?

Limitations of cherry-pick workflows include potential merge conflicts and duplicated history if not managed carefully. Cherry-picking isolated changes requires validation checks and backup workflows to maintain robust repositories and prevent data loss.