agentsclimarketplace

Regitize date customize

Skill gadost/regitize/skills/regitize-date-customize

Portable AI-agent skills for auditing and improving Git history

Install
npx -y skills add gadost/regitize --skill regitize-date-customize

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

Redistribute Git author and committer dates evenly across a branch, starting at a user-supplied date and ending at today, while preserving snapshots and merge topology. Use when the user invokes regitize-date-customize with a start date, asks to stretch or spread commits over time, or wants historical commit timestamps normalized into a chosen date range.

SKILL.md

2.9 KB, as published. Nobody here has run it

Regitize Date Customize

Rewrite commit timestamps without changing messages, authors, file trees, or merge topology. Never push rewritten history.

Workflow

  1. Obtain start-from-date from the invocation or user request. Accept YYYY-MM-DD or an ISO 8601 timestamp. If absent, ask for it.

  2. Locate this skill directory so its bundled scripts can be executed by absolute path.

  3. Verify the repository and target branch. Default to the current local branch. Refuse a detached HEAD unless the user names a local branch.

  4. Inspect git status --short and git log --graph --decorate --format='%h %aI %cI %s'.

  5. Run:

    node <skill-dir>/scripts/plan-dates.mjs <start-from-date> --output <repo-git-dir>/regitize/date-plan.json

    Add --end <ISO-date> only if the user explicitly requested an endpoint other than now. Add --dates author or --dates committer only when requested; the default rewrites both.

  6. Run node <skill-dir>/scripts/rewrite-history.mjs --plan <plan-path> without --apply to validate.

  7. Show the user the branch, number of commits, exact start and end instants, rewritten fields, first three scheduled commits, and last three scheduled commits. Explain that all descendant SHAs will change. Dates are generated in UTC; a date-only start means local midnight converted to UTC.

  8. Stop and obtain explicit approval for that exact schedule.

  9. After approval only, run the same rewrite command with --apply. If the history contains signatures or special commit metadata, obtain the separate acknowledgement requested by the validator and update the plan flags described in references/date-behavior.md.

  10. Verify the new log and report the old head, new head, and backup ref. Do not force-push unless the user separately asks for it.

Scheduling rules

  • Order commits parent-before-child using Git topological order.
  • For two or more commits, place the first exactly at the start and the last exactly at the end; distribute the rest at equal time intervals.
  • For one commit, use the end instant because one point cannot occupy both endpoints.
  • Rewrite both author and committer dates by default.
  • Do not alter messages, identities, trees, parent relationships, branches, or tags.
  • Regenerate the plan if expectedHead no longer matches.

Resources

  • scripts/plan-dates.mjs produces the deterministic schedule and JSON plan.
  • scripts/rewrite-history.mjs validates and applies the approved plan.
  • references/date-behavior.md defines parsing, plan flags, and recovery.

Gives 0 of the 12 instructions most pr commit review skills give

Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-06

  • use conventional commits formatin 123 of 888, across 110 files
  • keep subject line under 72 charactersin 60 of 888, across 46 files
  • delete branches after mergein 50 of 888, across 37 files
  • use imperative mood in subject linein 50 of 888, across 41 files
  • use imperative mood in commit messagesin 45 of 888
  • generate a conventional commit messagein 42 of 888
  • make atomic commitsin 37 of 888, across 25 files
  • run tests before committingin 36 of 888, across 24 files
  • run project test suite to verify clean baselinein 35 of 888, across 7 files
  • run detected project setup commandsin 34 of 888, across 6 files
  • wrap commit body at 72 charactersin 32 of 888, across 25 files
  • split unrelated changes into separate commitsin 32 of 888, across 27 files

Said here and by no other author read

  • obtain a start date before proceeding
  • refuse a detached head without a named branch
  • run the date planning script to produce a json plan
  • run the rewrite script without apply to validate
  • show the schedule and warn that shas will change
  • stop and obtain explicit user approval for the schedule

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

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.