agentsclimarketplace
Sign in

Regitize squash

Skill gadost/regitize/skills/regitize-squash

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.From its SKILL.md

Install
npx -y skills add gadost/regitize --skill regitize-squash

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 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.

SKILL.md

2.1 KB, 356 tokens by cl100k_base, 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

  1. Locate this skill directory and select a local branch, defaulting to the current branch.
  2. Run node <skill-dir>/scripts/collect-squash-context.mjs and read the entire generated JSON, including patches.
  3. 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.
  4. Keep commits separate when they can be reviewed or reverted independently, cross a merge boundary, affect distinct concerns, or have uncertain intent.
  5. Write and present a plan following references/plan-format.md. Include preserved commits as well as squash groups so omissions are visible.
  6. 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.
  7. 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.

What ships with it: 4 files

5.5 KB alongside SKILL.md, 2 of them executable

agents/

references/

scripts/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.