agentsclimarketplace

Regitize authors

Skill gadost/regitize/skills/regitize-authors

Portable AI-agent skills for auditing and improving Git history

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

Assembled 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

Normalize historical Git author names and email addresses from repository .mailmap rules, preview every identity change, and safely rewrite one local branch after explicit approval. Use when the user invokes regitize-authors, asks to apply .mailmap permanently to commit history, wants duplicate author identities consolidated, or needs historical author metadata corrected.

SKILL.md

2.0 KB, as published. Nobody here has run it

Regitize Authors

Apply .mailmap identity rules to commit objects. Default to author identities only; include committers only when explicitly requested.

Workflow

  1. Confirm that .mailmap rules or mailmap.file configuration represent the desired canonical identities. Do not guess canonical names or emails.
  2. Locate this skill directory and select one local branch, defaulting to the current branch.
  3. Run node <skill-dir>/scripts/plan-authors.mjs. Add --identities both only when the user asks to normalize committers too.
  4. Read the plan and show every distinct before-to-after identity mapping plus affected commit counts. If there are no changes, stop without rewriting.
  5. Validate with node <skill-dir>/scripts/rewrite-authors.mjs --plan <plan-path> without --apply.
  6. Explain that commit SHAs and descendant SHAs will change, other branches/tags remain untouched, and signatures cannot remain valid.
  7. Obtain explicit approval for the exact mapping and branch.
  8. After approval only, run the validator with --apply. Set signature or metadata acknowledgement flags only after separate explicit acceptance when requested.
  9. Verify git log --format='%H %an <%ae> | %cn <%ce>', then report the backup ref, old head, and new head. Never push automatically.

Safety rules

  • Preserve messages, timestamps, trees, and merge topology.
  • Do not infer mappings from similarity; use only git check-mailmap results.
  • Rewrite one local branch per invocation.
  • Regenerate if expectedHead is stale.

See references/mailmap.md for mapping and recovery behavior.

Keep looking

Skills are one crate of 328,083. 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.