git-advanced-workflows

Interactive rebasing cleans up commit history on a feature branch by letting you squash, reorder, or edit commits before merging. This Skill automates the rebase workflow with built-in validation and fail-safes to prevent history loss or merge conflicts.

To recover lost commits or undo changes in Git, you use the reflog to track reference updates and find orphaned commits. This Skill automates reflog workflows to diagnose history errors and restore lost work safely with guided validation.

Git bisect identifies the specific commit that introduced a bug by performing a binary search through your commit history. This Skill guides the bisect workflow, automating the process of marking commits as good or bad to isolate the defective change.

Yes, you can safely cherry-pick changes across multiple branches to synchronize features. This Skill applies safe cherry-picking workflows with validation and fail-safes to ensure changes integrate cleanly without duplicating commits or corrupting branch history.

Git worktrees allow you to check out multiple branches simultaneously in separate directories, streamlining multi-branch development and bugfix cycles. This Skill automates worktree workflows so you can context-switch between features without stashing changes.

You should avoid rebasing commits that have already been pushed and shared with collaborators, as rewriting public history causes conflicts. This Skill provides fail-safes and guidance to identify when rebasing is unsafe and suggests alternative history cleanup approaches.