# 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.

- Skill: `standardharness/release-notes` (Agent Skill)
- Install (CLI): `npx skillmds@latest add standardharness/release-notes`
- Raw SKILL.md: https://api.skillmd.com/api/skills/standardharness/release-notes/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: standardharness (https://skillmd.com/u/standardharness)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/standardharness/release-notes

---


# 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.