git-advanced-workflows
Master advanced Git workflows and recovery
Advanced Git history tasks can be risky and time consuming. This skill provides clear guidance for rebase, cherry-pick, bisect, worktrees, and reflog recovery.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "git-advanced-workflows". I reset to the wrong commit and lost work. How do I recover it?
Expected outcome:
- Run git reflog and identify the commit before the reset
- Create a recovery branch at that commit hash
- Verify changes and continue work from the recovery branch
Using "git-advanced-workflows". How do I apply a security fix to three release branches at once?
Expected outcome:
- Create fix on main branch first
- Check out each release branch and cherry-pick the fix commit
- Handle any conflicts per branch
- Test each branch before pushing
Security Audit
SafeDocumentation-only skill containing pure instructional content about Git workflows. No executable code, network calls, file access, or environment variable reads were found. All content is educational text explaining Git commands. Static findings are false positives triggered by documentation patterns, hash identifiers, and markdown code blocks.
Risk Factors
🌐 Network access (1)
⚙️ External commands (41)
📁 Filesystem access (6)
Quality Score
What You Can Build
Clean feature branch history
Prepare a linear commit history before opening a pull request.
Backport a hotfix safely
Apply one fix across multiple release branches with cherry-pick steps.
Locate a regression commit
Use bisect steps to find the commit that introduced a bug.
Try These Prompts
Show the exact interactive rebase steps to squash and reword my last five commits safely.
Explain how to cherry-pick a specific commit onto release/2.0 and how to continue after conflicts.
Give a step by step git bisect workflow using a test command to locate a regression.
Describe how to use worktrees for parallel branches and how to recover a lost commit with reflog.
Best Practices
- Create a backup branch before risky history edits
- Use --force-with-lease when rewriting shared history
- Keep commits small and descriptive for easier recovery
Avoid
- Rebasing public branches used by collaborators
- Force pushing without checking remote updates
- Running bisect with a dirty working directory