Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
84
74%
Does it follow best practices?
Impact
88%
1.00xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/developer-essentials/skills/git-advanced-workflows/SKILL.mdInteractive rebase and autosquash PR prep
Backup branch created
100%
100%
Autosquash flag used
0%
0%
Interactive rebase used
100%
100%
Rebase not merge for cleanup
100%
100%
force-with-lease push
100%
100%
Test or verification step
100%
100%
Rebase base targets main
100%
100%
--force-with-lease rationale
100%
100%
Backup branch rationale
100%
100%
Rebase squash/fixup operations
100%
100%
Commit message reword
100%
100%
Automated bisect bug investigation
bisect start command
100%
100%
bisect bad marked
100%
62%
bisect good marked
100%
62%
bisect run used
100%
100%
test script exit 0 for good
100%
100%
test script non-zero for bad
100%
100%
bisect reset called
100%
100%
Clean working directory
100%
0%
Bad commit identified
100%
100%
Bisect explanation
100%
100%
Hotfix backport via worktrees and cherry-pick
worktree add used
100%
100%
Multiple worktrees
100%
100%
cherry-pick for full backport
0%
100%
Partial apply for 1.8
100%
100%
force-with-lease push
0%
0%
worktree remove or prune
100%
100%
No main-branch checkout
100%
100%
Backport log produced
100%
100%
All three releases addressed
100%
100%
Sanitizer applied to 1.8
100%
100%
Reflog recovery of lost commits
reflog command used
100%
100%
Lost commits located
100%
100%
Reset used for recovery
100%
100%
reflog output saved
100%
100%
90-day retention mentioned
100%
100%
Reflog mechanism explained
100%
100%
Reset vs branch recovery
100%
100%
Identifying correct hash
100%
100%
Commands explained
100%
100%
Script is executable
100%
100%
Feature branch sync via rebase strategy
git fetch included
100%
100%
Rebase used for sync
100%
100%
No merge for sync
100%
100%
Feature branch checked out
100%
100%
Linear history explained
100%
100%
When rebase is appropriate
100%
100%
When merge is appropriate
100%
100%
Rebase-only-local warning
100%
100%
Command sequence included
100%
100%
Script is executable
100%
100%
Split commit into atomic commits
Interactive rebase used
0%
0%
Edit marker applied
0%
0%
git reset HEAD^ used
100%
100%
Files staged separately
100%
100%
Multiple atomic commits
100%
100%
Descriptive commit messages
100%
100%
Rebase continued
0%
0%
Final log saved
100%
100%
reset HEAD^ explained
100%
100%
Atomic commits rationale
100%
100%
70444e5
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.