agentsclimarketplace

Release notes writer

Skill sisodiabhumca/agent-skills/skills/release-notes-writer

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-writer

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

Use to assemble user-facing release notes from a list of merged PRs (CSV/JSON) or by reading `git log` between two refs. Groups changes into Features / Improvements / Fixes / Breaking, drops internal-only items, links each line back to its PR, and produces both a public Markdown and a Slack-ready short version. Vendor-neutral.

SKILL.md

1.8 KB, as published. Nobody here has run it

Release Notes Writer

When to invoke

  • "Generate release notes for v3.2."
  • "What's in this release? Group changes for the changelog."
  • "Draft user-facing notes between v1.4.0 and main."

Inputs needed

  1. Source — one of:
    • CSV / JSON of merged PRs (number, title, body, labels, author, url)
    • Two git refs (e.g. v1.4.0..HEAD) — uses git log
  2. Audience — public (default; drops chore/internal) or internal (keeps everything).
  3. Version + date.

Workflow

  1. Ingest the change list.
  2. Classify each item: Feature, Improvement, Fix, Breaking, Internal.
    • Use Conventional-Commit prefixes (feat:, fix:, chore:, BREAKING CHANGE) when present.
    • Otherwise infer from labels and title verbs.
  3. Filter out internal items if audience=public.
  4. Render:
    • RELEASE_NOTES.md — sectioned Markdown with PR links
    • SLACK.md — 3-bullet TL;DR
  5. Highlight breaking changes at the top with explicit migration callouts.

Output format

## Highlights
## Breaking changes
## New features
## Improvements
## Bug fixes
## Internal (omitted from public notes)

Guardrails

  • Never invent or rewrite a PR title beyond minor copy editing.
  • Always link back to the PR number / URL.
  • Breaking changes get their own section even if there's only one.

Reference code

generate.py reads CSV/JSON or git log, classifies, and writes both Markdown outputs.

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.