Regitize squash
Portable AI-agent skills for auditing and improving Git history
npx -y skills add gadost/regitize --skill regitize-squashAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Analyze a Git branch for fixup, squash, checkpoint, WIP, typo-only, formatting-only, and tightly coupled follow-up commits, then produce a semantic squash plan without changing history. Use when the user invokes regitize-squash, asks which commits should be combined, wants a cleanup plan before interactive rebase, or needs noisy history grouped into reviewable changes.
SKILL.md
2.1 KB, as published. Nobody here has run it
Regitize Squash Plan
Produce an evidence-based plan only. Do not rebase, reset, or update refs unless the user separately requests execution after reviewing the plan.
Workflow
- Locate this skill directory and select a local branch, defaulting to the current branch.
- Run
node <skill-dir>/scripts/collect-squash-context.mjsand read the entire generated JSON, including patches. - Identify groups only when commits represent one coherent change. Strong signals include explicit
fixup!/squash!, a small correction to the immediately preceding change, identical file focus, or a checkpoint sequence with no independent value. - Keep commits separate when they can be reviewed or reverted independently, cross a merge boundary, affect distinct concerns, or have uncertain intent.
- Write and present a plan following references/plan-format.md. Include preserved commits as well as squash groups so omissions are visible.
- For every group, state the target commit, absorbed commits in chronological order, combined message, evidence, and risk. Flag shared refs, merges, and non-contiguous groups.
- Stop after the plan. If the user asks to apply it, treat that as a new history-rewrite operation: create a backup ref, re-check the head, show the exact rebase sequence, and obtain explicit confirmation.
Decision rules
- Prefer the smallest defensible group.
- Never squash solely because a commit is small.
- Never move changes across merge parents in a plan presented as mechanically safe.
- Treat typo/formatting commits as squash candidates only when they clearly repair the same nearby change.
- Do not invent a dependency from overlapping filenames alone; confirm with patch semantics.