git-advanced-workflows

Perform complex Git operations like rebase, cherry-pick, bisect, worktrees, and reflog recovery.

4|Updated May 1, 2026
One-click install
npx skills add https://github.com/HigorAlves/orc --skill git-advanced-workflows-higoralves
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-advanced-workflows
Source: https://github.com/HigorAlves/orc/tree/main/orc/skills/git-advanced-workflows
Command: npx skills add https://github.com/HigorAlves/orc --skill git-advanced-workflows-higoralves

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers manage complex Git histories, recover lost commits, and streamline multiple branch workflows, reducing errors and saving time.

Core Features & Use Cases

  • Advanced Git Operations: Including rebase, cherry-pick, bisect, worktrees, and reflog for sophisticated repository management.
  • Troubleshooting & Recovery: Guided techniques to revert or recover from mistakes, such as accidents in commits or branch deletions.
  • Use Case: When working on a feature branch, clean its history before creating a pull request, or find the exact commit that introduced a bug using bisect.

Quick Start

Use the git advanced workflows skill to perform an interactive rebase to clean up your feature branch history.

Frequently Asked Questions about git-advanced-workflows

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

FAQPage Schema
How do I use git bisect to find the exact commit that introduced a bug?

Git bisect systematically narrows down repository history to locate the specific commit introducing an error. This Skill guides developers through the binary search process, automating commit checks to pinpoint regression causes efficiently.

What is the best way to clean up feature branch history before a pull request?

Cleaning feature branch history requires an interactive rebase to squash or reorder commits. This Skill provides guided techniques for executing risky rebase operations safely, ensuring a streamlined and coherent commit history before merging.

How do I recover lost commits after an accidental branch deletion or hard reset?

Recovering lost commits relies on the git reflog to trace HEAD movements. This Skill applies reflog recovery techniques to restore deleted branches and retrieve seemingly lost repository states, preventing data loss.

Can I work on multiple branches simultaneously without cloning the repository again?

Git worktrees allow developers to check out multiple branches simultaneously in separate directories. This Skill enables efficient multiple branch workflows, eliminating the need to clone the repository multiple times for parallel development.

Do I need command-line Git experience to use advanced workflows like cherry-pick and rebase?

Yes, performing complex git operations like cherry-pick, rebase, and worktrees requires familiarity with command-line Git. This Skill is designed for developers executing manual version control commands and repository management scripts.

Why should I use git worktrees instead of stashing changes for context switching?

Git worktrees provide isolated directories for separate branches, avoiding the risks of stashing and switching. This Skill helps manage multiple branch workflows efficiently, reducing errors and saving time during context switches.