git-advanced-workflows

Automate advanced Git workflows across branches for clean history.

Updated Dec 8, 2025
One-click install
npx skills add https://github.com/sduduzog/.dotfiles --skill git-advanced-workflows-sduduzog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-advanced-workflows
Source: https://github.com/sduduzog/.dotfiles/tree/main/agents/skills/git-advanced-workflows
Command: npx skills add https://github.com/sduduzog/.dotfiles --skill git-advanced-workflows-sduduzog

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill teaches advanced Git techniques to clean up history, cherry-pick changes across branches, and recover from mistakes, enabling teams to maintain coherent and reliable repositories.

Core Features & Use Cases

  • Interactive Rebase: edit, squash, reword, and reorder commits to produce a clean history.
  • Cherry-Picking & Cross-Branch Changes: selectively apply commits to different branches while handling conflicts.
  • Bisect & Reflog Recovery: locate and recover from introducing commits and restore lost work.
  • Worktrees & Parallel Development: manage multiple checked-out branches without stashing or switching contexts.

Quick Start

Configure and execute an advanced Git workflow in your repository for a feature branch and its related release branches.

Frequently Asked Questions about git-advanced-workflows

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

FAQPage Schema
How do I squash commits using interactive rebase to clean up a feature branch?

Interactive rebase allows you to edit, squash, reword, and reorder commits to produce a clean history before merging a feature branch. This skill automates these advanced Git workflows to preserve navigable repository history.

Can I manage multiple checked-out branches simultaneously using Git worktrees?

Git worktrees enable parallel development by managing multiple checked-out branches simultaneously without stashing or switching contexts. This skill provides guidance and commands for setting up worktrees to streamline cross-branch workflows.

What is the best way to locate a bug-introducing commit in my version control history?

Git bisect is the best way to locate a bug-introducing commit by systematically narrowing down the version control history. This skill documents bisect commands to help identify exactly when changes were introduced.

How do I recover lost work after a failed Git rebase or hard reset?

You can recover lost work after a failed Git rebase or hard reset by using the Git reflog to restore lost commits. This skill includes reflog guidance with concrete examples to help recover from mistakes.

How do I cherry-pick changes across different branches while resolving conflicts?

Cherry-picking selectively applies specific commits to different branches while handling conflicts during the process. This skill supports cross-branch cherry-picking to help you maintain coherent and reliable repositories.

Do I need any external dependencies to manage advanced Git workflows like rebase and bisect?

No external dependencies are required to manage advanced Git workflows like rebase and bisect. This skill uses built-in Git commands and provides scripts and references to automate history cleanup and recovery directly in your repository.