skills.rest
duanbiao2000
duanbiao2000COMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-advanced-workflows

Perform interactive rebases, cherry-picks, bisect sessions, worktree management, and reflog recovery.

3|1|Updated Feb 3, 2026
Search Tags:#git#worktrees#reflog#cherry-pick#bisect#version-control#rebasing
One-click install
npx skills add https://github.com/duanbiao2000/obsidianDoc26 --skill git-advanced-workflows-duanbiao2000
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-advanced-workflows
Source: https://github.com/duanbiao2000/obsidianDoc26/tree/main/agents-main/plugins/developer-essentials/skills/git-advanced-workflows
Command: npx skills add https://github.com/duanbiao2000/obsidianDoc26 --skill git-advanced-workflows-duanbiao2000

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Helps developers maintain clean Git histories and coordinate complex changes across branches, reducing merge conflicts and accidental regressions.

Core Features & Use Cases

  • Interactive Rebase: rewrite commit history to group related changes into logical commits.
  • Cherry-Picking: apply commits across branches without merging entire histories.
  • Bisect: locate bug introducers efficiently using binary search.
  • Worktrees: develop on multiple branches simultaneously.
  • Reflog: recover from lost commits or reset states.

Quick Start

Start on a feature branch and run the recommended workflow to clean up history before opening a pull request.

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 an interactive rebase to clean up my commit history before a pull request?▼

Use an interactive rebase to rewrite commit history, grouping related changes into logical commits. This streamlines multi-branch development by ensuring a clean and coherent history before opening a pull request.

What's the best way to apply a hotfix commit across multiple branches without merging histories?▼

Cherry-picking applies specific commits across branches without merging entire histories. It is the recommended workflow for propagating hotfixes and collaborative feature work, preventing accidental regressions and reducing merge conflicts.

How does git bisect locate the commit that introduced a bug?▼

Git bisect locates bug introducers efficiently using a binary search through your commit history. It systematically narrows down the regression point by testing intermediate commits, pinpointing the exact problematic change.

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

Git worktrees allow you to develop on multiple branches simultaneously without stashing. This workflow manages multi-branch development efficiently, improving history clarity and conflict resolution during collaborative feature work.

How do I recover lost commits or undo a hard reset in version control?▼

Use the git reflog to recover from lost commits or reset states. It records updates to the tip of branches, allowing you to restore previous HEAD states and safely coordinate complex changes across branches.

Related Skills

Explore More Software Engineering Skills→
ckyeonckyeon

check-updates

Compare pinned commits against upstream HEAD and investigate tracked path changes.

Community
Intermediate
ZacharyLuzZacharyLuz
5

git

Coordinates Git workflows with sequenced commits, controlled merges, and structured handoffs to teammates.

Community
Basic
kos3nzkos3nz

git-advanced-workflows

Automate interactive rebase, cherry-picking, bisect, worktrees, and reflog recovery for clean Git history.

Community
Advanced
theslashdojotheslashdojo

git-rebase

Replay commits onto a new base with interactive rebase and autosquash.

Official
Intermediate