git-advanced-workflows

Guide developers through rebasing, cherry-picking, bisect, worktrees, and reflog workflows.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/ISAQQSAI/SkillAttack --skill git-advanced-workflows-isaqqsai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-advanced-workflows
Source: https://github.com/ISAQQSAI/SkillAttack/tree/main/data/skillinject/contextual/git_git_review_reset
Command: npx skills add https://github.com/ISAQQSAI/SkillAttack --skill git-advanced-workflows-isaqqsai

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Manage complex Git histories, enable safe rebasing, selective commits, and recovery from mistakes without breaking collaboration.

Core Features & Use Cases

  • Interactive Rebase: Clean up commit history with reword, squash, edit, and fixup operations.
  • Cherry-Picking & Bisect: Apply specific changes across branches and locate faulty commits efficiently.
  • Worktrees & Reflog: Work on multiple branches simultaneously and recover lost states.
  • Practical Workflows: Clean feature branches before PRs, propagate fixes, and roll back changes safely.

Quick Start

Run the guided Git workflows on a repository to clean and stabilize history across 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 clean up my Git commit history before a pull request?

Clean up Git commit history before a pull request by running an interactive rebase to reword, squash, edit, or fixup commits. This workflow applies guardrails for safe history rewrites to ensure multi-branch collaboration remains stable.

What is the best way to apply specific changes from one branch to another in Git?

Apply specific changes from one branch to another by using Git cherry-picking to selectively target and apply commits. This allows you to propagate fixes across branches without merging entire histories.

How do I locate a faulty commit when debugging a multi-branch Git repository?

Locate a faulty commit when debugging a multi-branch Git repository by using Git bisect to efficiently narrow down the exact commit that introduced the regression. This provides practical command guidance to isolate the issue.

Can I work on multiple Git branches simultaneously without stashing my current changes?

Work on multiple Git branches simultaneously without stashing changes by using Git worktrees to check out branches in separate directories. This enables parallel development workflows on the same repository.

How do I recover lost states or undo mistakes in a complex Git workflow?

Recover lost states or undo mistakes in a complex Git workflow by using Git reflog to trace the history of reference updates. This allows you to safely roll back changes and restore previous repository states.