Release Notes

Draft public changelog or release notes from git history. Use when the user asks for a changelog, release post, or "what shipped". Never dump internals, paths, or session identifiers into the notes.

standardharness Updated

File contents

Release notes

Write for people who were not in the repo.

Sources

  • git log on the range the user named (tag, branch, or SHA).
  • Existing CHANGELOG.md or docs/releases/ if present.

Do not quote private tracker comments, local paths, or tool transcripts.

Shape

  • What changed, in user terms.
  • Why it matters, one line when it is not obvious.
  • Breaking changes called out first.

Skip chore-only commits unless they are the whole release.

Public bar

No session or run ids, no absolute machine paths, no provider or account detail, no paste of a user message. An issue mention is enough for a bugfix.

standardharness/skills/tree/main/skills/release-notes commit 9fb14c7355

Frequently asked questions

npx skillmds@latest add standardharness/release-notes