git-advanced

Perform advanced Git operations and recovery techniques for complex history issues.

3|Updated Feb 6, 2026

Search Tags:#git #recovery #reflog #rebase #advanced #cherry-pick #bisect

Ready to run

npx skills add https://github.com/1Mangesh1/dev-skills-collection --skill git-advanced-1mangesh1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-advanced
Source: https://github.com/1Mangesh1/dev-skills-collection/tree/main/skills/git-advanced
Command: npx skills add https://github.com/1Mangesh1/dev-skills-collection --skill git-advanced-1mangesh1

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Advanced Git operations and recovery techniques to fix complex history issues, recover lost work, and maintain safe collaboration.

Core Features & Use Cases

Interactive rebase, cherry-pick, bisect, and reflog-based recovery for feature branches and releases
History cleanup, commit squashing, and safe undo/redo of changes
Real-world scenarios with guidance on recovering lost commits, fixing history, and resolving conflicts

Quick Start

Ask me to guide you through an interactive rebase of your current branch onto a target base and resolve conflicts.

Frequently Asked Questions about git-advanced

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

FAQPage Schema

How do I recover lost commits after a hard reset or failed rebase?▼

Recover lost commits using git reflog and ORIG_HEAD tracking to restore dropped history. This skill guides you through reflog-based recovery to find dangling commits and safely undo complex history issues on feature branches.

What is the best way to squash multiple commits before merging a feature branch?▼

The best way to squash commits is an interactive rebase to clean up history before merging. This skill provides safe rebase workflows to squash, edit, and reorder commits while resolving conflicts on release branches.

How do I use git bisect to find which commit introduced a bug?▼

Use git bisect to perform a binary search through your commit history to isolate the bug. This skill helps you run bisect across feature branches to identify exactly when a complex issue was introduced.

Can I cherry-pick specific commits from one branch to another without merging?▼

You can cherry-pick specific commits to apply targeted changes across branches without a full merge. This skill provides guidance on cherry-picking workflows and resolving conflicts when moving changes between release branches.

When should I not use git rebase to fix history issues?▼

Avoid git rebase on shared branches to prevent overwriting published history and causing conflicts. Use reflog recovery and ORIG_HEAD tracking to safely undo changes instead of forcing complex history issues on collaborators.