Rewrite Git commit history non-interactively using git rebase -i automation.
npx skills add https://github.com/alexanderguy/skills --skill git-rebase-alexanderguy
Please help me install this Agent Skill. Skill: git-rebase Source: https://github.com/alexanderguy/skills/tree/main/skills/git-rebase Command: npx skills add https://github.com/alexanderguy/skills --skill git-rebase-alexanderguy
It solves the problem of messy or incorrect Git branch history by enabling safe, non-interactive rewriting of commits that are not at HEAD.
git rebase -i editor invocations via GIT_SEQUENCE_EDITOR so the rebase completes without human keyboard input.Use Case: You discover an earlier commit message is misleading and that a feature was bundled with unrelated changes; you rewrite that commit and split it into cleaner, reviewable commits before pushing.
Use the git-rebase skill to rewrite a branch’s commit history non-interactively by scripting git rebase -i so you can drop, split, and reword commits and validate the result against a pre-rebase backup.
High-intent search queries and answers about installing and using this skill.
To squash or drop old commits non-interactively, use automated git rebase -i scripting via GIT_SEQUENCE_EDITOR. This approach drives the rebase editor deterministically without human keyboard input, allowing you to replay commits with specific squash or drop actions.
The safest way to rewrite Git commit history is creating backup branches before starting, using automated rebase scripting for deterministic replay, and validating diffs against the pre-rebase backup to confirm no content was lost during the rewrite.
To fix a misleading commit message mid-branch, perform a non-interactive reword operation using automated git rebase -i. By scripting GIT_EDITOR and GIT_SEQUENCE_EDITOR, you can reword specific commits deterministically without opening an interactive editor.
Yes, splitting a bundled commit is possible through non-interactive rebase automation. The git-rebase approach supports splitting and fixups via deterministic scripting patterns, allowing you to separate unrelated changes into reviewable commits before pushing.
An automated git rebase -i stops with a paused or zombie state due to unresolved conflicts or incomplete previous operations. Safety checks can detect these zombie rebases, advising explicit diff validation and resolution before continuing the history rewrite.
Yes, non-interactive rebase works for pre-push cleanup by using GIT_SEQUENCE_EDITOR and GIT_EDITOR environment variables. This enables deterministic editor driving, allowing you to rewrite history and validate commits automatically without manual keyboard input.
pelchersCreate and push savepoint branches from the current commit state.
sluongngReconcile local fork patches against upstream with safety branches and per-commit validation.
Alex1980AlexAutomatically run git add and commit when a file-change threshold is reached.
biwsantangPerform interactive git rebases with conflict resolution guidance and backups.