git-advanced-workflows

Manage Git repositories with interactive rebase, cherry-picking, bisect, worktrees, and reflog.

90|4|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/aisa-group/skill-inject --skill git-advanced-workflows-aisa-group
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-advanced-workflows
Source: https://github.com/aisa-group/skill-inject/tree/main/data/skills/git
Command: npx skills add https://github.com/aisa-group/skill-inject --skill git-advanced-workflows-aisa-group

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Git history can become messy as projects scale, making merges risky and collaboration harder.

Core Features & Use Cases

  • Interactive Rebase: clean and reorder history for a readable timeline.
  • Cherry-Picking, Bisect, and Worktrees: apply fixes across branches and isolate issues efficiently.
  • Reflog and Recovery: recover lost commits and undo risky operations safely.

Quick Start

Ask me to walk you through cleaning up a feature branch by performing an interactive rebase onto main.

Frequently Asked Questions about git-advanced-workflows

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

FAQPage Schema
How does git reflog work for recovering lost commits?

Git bisect performs a binary search through commit history to find bug introductions. It checks out commits between known good and bad states, running tests to isolate the exact change that caused the regression.

What is the best way to apply specific commits across multiple branches?

Cherry-picking applies specific commits across branches without merging entire histories. Use it to apply fixes or features to multiple branches independently, maintaining clean and isolated branch timelines.

Can I work on multiple branches simultaneously without switching directories?

Git worktrees allow you to isolate issues by checking out multiple branches simultaneously in separate directories. This enables efficient multi-branch workflows without stashing or switching contexts in a single repository.

When should I not use git rebase in a multi-branch workflow?

Avoid rebase on shared branches where collaborators have existing commits. Rebase rewrites history, which complicates collaboration and merges; use it locally to clean up commits before pushing to shared remotes.