release-notes
/release-notes
Write release notes or a changelog entry from git history. Use when the user asks for release notes, a changelog, "what changed since the last release", or a summary of commits between two tags or branches.
- Author
- narayana006 ↗
- Repository
- agent-skills-collection ↗
- Licence
- MIT
- Last repository change
- 10.11.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/collect_commits.py
What it does and when to use it
Write release notes or a changelog entry from git history. Use when the user asks for release notes, a changelog, "what changed since the last release", or a summary of commits between two tags or branches.
Triggers from the description
Original author description
Write release notes or a changelog entry from git history. Use when the user asks for release notes, a changelog, "what changed since the last release", or a summary of commits between two tags or branches.
How it works
- Steps
- Output format
SKILL.md preview
---
name: release-notes
description: Write release notes or a changelog entry from git history. Use when the user asks for release notes, a changelog, "what changed since the last release", or a summary of commits between two tags or branches.
---
# Release notes from git history
Turn a range of commits into notes a user of the project can read in a minute.
## Steps
1. **Pick the range.** If the user named two refs, use them. Otherwise use the latest tag up to
`HEAD`. Confirm the range in your answer.
2. **Collect the commits.** Run the bundled script from the repository root:
```bash
python3 scripts/collect_commits.py --from v1.2.0 --to HEAD
```
With no `--from` it starts at the most recent tag (or the first commit if there are no tags).
Add `--format json` if you want to process the result yourself. The script groups commits by
conventional-commit type and lists breaking changes first. Details are in
[the commit grouping reference](reference.md).
3. **Read what is unclear.** For any commit whose subject does not explain the user-visible
effect, look at the diff (`git show --stat <hash>`) before writing about it.
4. **Write the notes.**
- Lead with breaking changes and what the user must do about each.
- Then features, then fixes. Fold docs, tests, CI and refactors into one "Internal" line or
leave them out.
- One line per change, written for users: the effect, not the implementation.
"Exports no longer time out on large projects", not "refactor ExportJob retry loop".
- Merge commits that belong to one change into one line.
- Keep issue or pull request numbers that appear in the subjects.
5. **Check before you hand it over.** Every line maps to at least one commit in the range, nothing
is invented, and the version and date in the heading are the ones the user gave you. If you
were not given a version number, ask or leave a clear placeholder.
## Output format
```markdown
## v1.3.0 (2025-03-14)
### Breaking changes
- ...
### Added
- ...
### Fixed
- ...
```
Follow the project's existing CHANGELOG style instead if it has one.
Files in this package (3)
- SKILL.md 2 KB
- reference.md 1 KB
- scripts/collect_commits.py 4 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · narayana006/agent-skills-collection | 100 | MIT |
| mono/SkiaSharp | 100 | MIT |
| niekcandaele/claude-helpers | 100 | MIT |
| kenryu42/cc-safety-net | 100 | MIT |
| zeitlos/lucity | 100 | AGPL-3.0 |
| openshift-pipelines/pipelines-as-code | 100 | Apache-2.0 |
| paperwingio/paperwing | 100 | Apache-2.0 |
| jelvodev/yaap | 100 | MIT |
| yearzen1/LocalSkillManager | 100 | MIT |
Database snapshot: 13.11.2026 · package version 742a05018333 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100changelog
Write release notes or a CHANGELOG.md entry from git history. Use when the user says "write the changelog", "release notes for v2.3", "what changed since the last release/tag", or is preparing a release or version bump. - 100changelog-from-tags
Generates release notes from git history between two tags, grouped by commit type. Use when the user asks for a changelog, release notes, or a summary of what changed since a version. - 85atlas-changelog
Writes what changed, from the git history and the pull requests, never from memory: a changelog entry in the project's format, the release notes for the people who use the thing, and the version the changes call for. Use for "atlas changelog", "release notes for this version",… - 100generate-release-notes
This skill should be used when the user asks to "generate release notes", "generate changelog", "create release notes", "write changelog", "what changed since last release", "prepare release notes", "update changelog", or "summarize changes from git history". Parses conventional… - 90changelog-writer
Read the git log and write a user-facing changelog entry in Keep a Changelog format. Use when the user wants to document what changed in a release, write release notes, or update their CHANGELOG.md. - 100trove-release-notes
Release notes generator. Creates user-facing release notes from git history, PR descriptions, and changelog entries. Use when: release notes; draft a changelog; what shipped; update changelog.