← Back to list

git-rebase
by mhalder
Modular Linux development environment dotfiles managed with tuckr, featuring shell configurations, development tools, and automated installation hooks
⭐ 1🍴 0📅 Jan 24, 2026
SKILL.md
name: git-rebase description: Guide interactive rebasing, commit squashing, and conflict resolution. Use when the user says "squash commits", "rebase onto main", "interactive rebase", "clean up commits", "fix commit history", or asks about rebasing. allowed-tools: Bash, Read
Git Rebase
Guide through interactive rebasing, squashing commits, and resolving conflicts.
Instructions
- Check current branch state:
git statusandgit log --oneline - Identify rebase target (main, specific commit, etc.)
- Guide through the rebase process step by step
- Help resolve conflicts if they occur
- Verify final state
Common operations
Squash last N commits
# Squash last 3 commits into one
git rebase -i HEAD~3
# In editor, change 'pick' to 'squash' (or 's') for commits to squash
# Keep 'pick' for the first commit
Rebase onto main
git fetch origin
git rebase origin/main
Rebase interactive options
pick = use commit
reword = use commit, but edit message
edit = use commit, but stop for amending
squash = meld into previous commit
fixup = like squash, but discard message
drop = remove commit
Conflict resolution
# See conflicting files
git status
# After fixing conflicts in files
git add <file>
git rebase --continue
# To abort and return to original state
git rebase --abort
# To skip a problematic commit
git rebase --skip
Safety checks
# Before rebasing, create backup branch
git branch backup-branch
# Check if branch has been pushed
git log origin/<branch>..<branch>
# If commits are pushed, warn about force push
Rules
- MUST check if commits have been pushed before rebasing
- MUST warn about force push requirements after rebasing pushed commits
- MUST suggest creating a backup branch for complex rebases
- Never use
-iflag (interactive mode not supported) - Never force push to main/master
- Never rebase public/shared branches without explicit approval
- Always show
git log --onelinebefore and after
Non-interactive alternatives
Since interactive mode (-i) requires manual editor input, use these instead:
# Squash all commits on branch into one
git reset --soft origin/main && git commit -m "message"
# Fixup a specific commit (auto-squash)
git commit --fixup=<commit>
git rebase --autosquash origin/main
# Reword last commit
git commit --amend -m "new message"
Score
Total Score
70/100
Based on repository quality metrics
✓SKILL.md
SKILL.mdファイルが含まれている
+20
✓LICENSE
ライセンスが設定されている
+10
✓説明文
100文字以上の説明がある
+10
○人気
GitHub Stars 100以上
0/15
○最近の活動
3ヶ月以内に更新がある
0/10
○フォーク
10回以上フォークされている
0/5
✓Issue管理
オープンIssueが50未満
+5
✓言語
プログラミング言語が設定されている
+5
○タグ
1つ以上のタグが設定されている
0/5
Reviews
💬
Reviews coming soon