Release notes changelog normalizer

Skill sisodiabhumca/agent-skills/skills/release-notes-changelog-normalizer

Production-Ready Agent Skills : product analytics, growth experiments, CRM, research synthesis, postmortems, data contracts, SaaS spend, compliance, architecture maps, and LLM eval and many more.

Install

npx -y skills add sisodiabhumca/agent-skills --skill release-notes-changelog-normalizer

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.

What its author says it does

Copied from the file, not written here

Vendor-neutral skill to normalize raw release notes into Keep a Changelog-style entries with consistent headings.

SKILL.md

1.0 KB, as published. Nobody here has run it

When to invoke

You have messy release notes from commits/tickets and need a clean changelog entry.
You need to standardize categories (Added/Changed/Fixed/Deprecated/Removed/Security).

Inputs needed

A JSON file with:
- version (string)
- date (string)
- items[] (strings), each a raw note line

Workflow

Normalize text: trim, de-duplicate, enforce sentence casing.
Classify each item into a changelog category using keyword heuristics.
Output a structured changelog entry suitable for inclusion in CHANGELOG.md.

Output format

Markdown text written to an output file.

Guardrails

Do not fabricate features; only reformat and categorize provided items.
Keep original meaning; avoid rewriting beyond light normalization.

Reference code

release_notes_changelog_normalizer.py reads JSON and writes a markdown changelog entry.

Gives 0 of the 12 instructions most ship operate skills give

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

document a rollback plan before deploymentin 40 of 779, across 21 files
create an annotated git tagin 21 of 779, across 20 files
Run the test suitein 20 of 779
update the changelogin 20 of 779, across 18 files
verify deployment health after launchin 19 of 779, across 10 files
clean up feature flags after full rolloutin 18 of 779, across 10 files
verify the working tree is cleanin 18 of 779
test both feature flag statesin 17 of 779, across 9 files
Make database migrations backward-compatiblein 16 of 779, across 8 files
set up error monitoring before launchin 15 of 779, across 7 files
monitor metrics at each rollout stagein 14 of 779, across 5 files
create a github releasein 14 of 779

Said here and by no other author read

normalize text by trimming duplicates and enforcing sentence casing
classify each item into a changelog category

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