git-mastery

Guide Git history rewriting with rebase, bisect, and reflog safety workflows.

161|21|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/softspark/ai-toolkit --skill git-mastery-softspark
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-mastery
Source: https://github.com/softspark/ai-toolkit/tree/main/app/skills/git-mastery
Command: npx skills add https://github.com/softspark/ai-toolkit --skill git-mastery-softspark

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git users often struggle with safely rewriting history, coordinating complex rebases, and recovering from mistakes in shared repos.

Core Features & Use Cases

  • Guided workflows for bisecting to identify buggy commits, interactive rebasing, and history reassembly with safety rails.
  • Safe recovery using reflog and guarded reset strategies to avoid data loss.
  • Enforced commit message conventions and best practices for collaboration.
  • Clear, action-oriented prompts to perform tasks like cherry-picking and conflict resolution.

Quick Start

Walk me through a safe, advanced Git history-rewriting scenario on a feature branch.

Frequently Asked Questions about git-mastery

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

FAQPage Schema
How do I safely rewrite Git history on a shared feature branch?

To safely rewrite Git history, use guided interactive rebasing workflows with safety rails like force-with-lease to prevent overwriting remote changes. This approach applies standard commit conventions while coordinating collaborative history edits across local and remote repositories.

How does Git reflog help recover from a bad rebase or reset?

Git reflog provides a chronological record of reference updates, enabling safe recovery from bad rebases or resets. By using guarded reset strategies alongside reflog, you can restore lost commits and avoid data loss during complex history reassembly.

What is the best way to find a buggy commit using Git bisect?

Git bisect identifies buggy commits by performing a binary search through your project history. Guided bisecting workflows automate the checkout and testing process, efficiently narrowing down the exact commit that introduced the regression.

Do I need to know advanced Git commands to use guided history rewriting workflows?

Yes, guided history rewriting workflows require knowledge of Git commands like bisect, rebase, reflog, cherry-pick, and reset. The workflows provide action-oriented prompts and safety practices to assist software development teams performing these complex operations.

How do I resolve conflicts when cherry-picking commits across feature branches?

Resolving conflicts during cherry-picking requires action-oriented prompts that guide you through standard conflict resolution workflows. This ensures collaborative history edits remain consistent across local and remote repositories while maintaining commit message conventions.