agentsclimarketplace

Regitize release notes

Skill gadost/regitize/skills/regitize-release-notes

Portable AI-agent skills for auditing and improving Git history

Install
npx -y skills add gadost/regitize --skill regitize-release-notes

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

Generate accurate user-focused release notes from a verified Git commit range by inspecting commit messages, patches, tags, and issue references. Use when the user invokes regitize-release-notes, asks for release notes or a changelog draft, wants changes summarized since a tag, or needs cleaned history converted into a publishable release summary.

SKILL.md

1.8 KB, as published. Nobody here has run it

Regitize Release Notes

Draft release notes from repository evidence. Prefer user-visible outcomes over a commit-by-commit transcript.

Workflow

  1. Determine the range. Respect explicit from and to refs. Otherwise use the latest reachable prior tag through HEAD; if no tag exists, include all reachable commits.
  2. Locate this skill directory and run node <skill-dir>/scripts/collect-release-context.mjs, adding --from, --to, and --output as required.
  3. Read every captured commit and patch. Exclude merge noise, duplicate descriptions, and internal-only work unless the audience needs it.
  4. Draft using references/release-format.md. Group by impact rather than commit order. Call out breaking changes, migrations, security fixes, and deprecations first.
  5. Preserve issue or PR identifiers found in history, but do not invent links, identifiers, performance numbers, or compatibility claims.
  6. Show the selected range and draft. Write the requested file, defaulting to RELEASE_NOTES.md only when the user asked for a file artifact.
  7. Report gaps where the diff demonstrates a change but its user impact cannot be established.

Quality rules

  • Combine multiple implementation commits into one outcome.
  • Use plain language and active voice.
  • Distinguish confirmed behavior from inference.
  • Omit empty sections.
  • Do not modify Git history, tags, releases, or remotes.

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.