Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From loopkit
Rebase, squash, or rewrite history without losing work or breaking shared branches. Use before any history rewrite.
How this skill is triggered — by the user, by Claude, or both
Slash command
/loopkit:rebase-safelyWhen to use
rebase, squash, "update my branch", interactive rebase, force-push
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. **Backup first** — `git branch backup/<name>` before any rewrite. Free undo.
git branch backup/<name> before any rewrite. Free undo.git fetch; git rebase origin/main.--force-with-lease, never bare --force (lease refuses if someone else pushed).
If anything goes sideways: git reflog finds the pre-rebase state; git reset --hard backup/<name> restores it.npx claudepluginhub archive228/loopkit --plugin loopkitProvides advanced git rebase patterns for linear history, stacked PRs, and commit history cleanup. Useful when rebasing branches, managing PR stacks, or fixing merge-heavy branches.
Rewrites a feature branch's messy commit history into clean, conventional commits that tell a progressive, linear story. Handles backup, soft reset, and atomic recommit.