git-advanced-workflows

Manage and rewrite Git commit history with interactive rebase, cherry-pick, bisect, and reflog.

Updated Dec 25, 2025

Search Tags:#git #version control #reflog #rebase #git history #cherry-pick #bisect

Ready to run

npx skills add https://github.com/mourato/prisma --skill git-advanced-workflows-mourato

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-advanced-workflows
Source: https://github.com/mourato/prisma/tree/main/.agents/skills/git-advanced-workflows
Command: npx skills add https://github.com/mourato/prisma --skill git-advanced-workflows-mourato

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) and scripts (resource) components.

What problem does it solve?

This Skill empowers users to manage and manipulate Git history with advanced techniques, ensuring clean commits, efficient collaboration, and robust recovery from errors.

Core Features & Use Cases

History Rewriting: Clean up commit messages, reorder, squash, or split commits using interactive rebase.
Selective Commits: Apply specific commits across branches with cherry-picking.
Bug Detection: Efficiently find the commit that introduced a bug using git bisect.
Recovery: Utilize git reflog to recover lost commits or branches.
Parallel Work: Manage multiple branches simultaneously with git worktree.

Quick Start

Use the git-advanced-workflows skill to clean up the last 5 commits on your current branch using interactive rebase.

Frequently Asked Questions about git-advanced-workflows

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

FAQPage Schema

How do I clean up and squash multiple commits using interactive rebase?▼

Interactive rebase lets you clean up commit history by reordering, squashing, splitting, or editing commit messages. You can rewrite the last several commits on a branch to ensure a clean and manageable project history before merging.

What is git bisect and how does it help find bugs?▼

Git bisect is a binary search mechanism used for bug detection across commit history. It systematically checks out commits between known good and bad states to efficiently pinpoint the exact commit that introduced a regression.

Can I recover lost commits or deleted branches with git reflog?▼

Git reflog records a history of reference updates, enabling robust recovery from errors. You can use reflog entries to locate and restore lost commits or accidentally deleted branches that are no longer visible in the standard branch log.

How do I apply specific commits from one branch to another?▼

Cherry-picking applies specific commits from one branch onto another. This selective commit application allows you to integrate isolated changes without merging an entire branch, supporting complex branching strategies and parallel development.

What is the best way to work on multiple branches simultaneously without switching?▼

Git worktree allows you to manage multiple branches simultaneously by linking separate working directories to a single repository. This enables parallel development workflows without needing to stash changes or switch branches repeatedly.

Do I need prior Git experience to use advanced history rewriting techniques?▼

Advanced history rewriting requires familiarity with standard version control operations. Because techniques like interactive rebase and cherry-picking manipulate commit history, users should understand basic branching and committing to avoid accidental data loss.