Indexed:437 news/102 AI tools/413 open-source projects/75 learning resources
HomeNewsOpen SourceModelsAI ToolsSkillsLearn
Home / Skills / Developer Productivity / Changelog Generator
Developer Productivity

Changelog Generator

ComposioHQ community contributorsApache-2.0Skill language: English
License verifiedNo scripts
DemoReal run · claude-sonnet-5-5 · October 2026
Create a changelog from the commits of the past 7 days for our notes app. This is for customers, not developers. We last released on 2026-09-28.
Skill: changelog-generator
Bash: git log --since=2026-09-28 --format='%h %ad %s' --date=short
Bash: ls CHANGELOG_STYLE.md CHANGELOG.md 2>&1

Updates: September 28 – October 4, 2026

✨ New Features

  • Shared Workspaces: Create a workspace for each project and invite your team, so everyone's notes stay organized in one place.
  • Keyboard Shortcuts: Press ? anywhere to see every available shortcut and move around faster without the mouse.

? Improvements

  • Better Search: Search now looks inside your notes, not just their titles.
  • Faster Sync: Syncing large folders is up to 2x faster.

? Security

  • Safer Shared Links: We strengthened protection on shared note links so that note titles can't be used to run malicious code.

? Fixes

  • Images larger than 10MB now upload properly. Previously they failed with a generic error.
  • The notification badge now resets correctly after you read your notifications.

I left out internal changes that don't affect customers: the ESLint upgrade, CI caching, sync queue refactoring and its tests. There was no CHANGELOG.md or style guide in the repo, so I haven't saved this to a file. I can write it to CHANGELOG.md if you'd like.

Real run recorded with claude-code / claude-sonnet-5-5. Run in a sample repository with 12 git commits, with Bash enabled to read the git history. Tool-call lines show only the first line of each command. The model output is unmodified.

What it does

Reads your git history for a date range or release and rewrites technical commits as clear release notes for customers.

How it works

  1. Scans the commits for the period you name, such as the past week or since a version.
  2. Groups them into features, improvements, fixes and security changes.
  3. Rewrites developer wording into customer language and leaves out internal changes such as refactoring, tests and tooling.
  4. Can follow your own style guide if you point it at one, for example a CHANGELOG_STYLE.md.

Good for

Release notes, weekly product updates, app store update text and a public changelog page.

Worth knowing

In our trial it grouped the 11 commits since the last release into four sections, left out the ESLint, CI and refactoring commits, and said so.

Notes & risks

Pure instruction file: no scripts. It runs git commands (such as git log) in your repository to read the history and writes nothing unless you ask it to save the result. Review the wording before you publish it, because it rewrites commit messages into claims about your product. The skill folder has no licence file of its own. The licence basis is the source repository's README, which declares the whole repository Apache-2.0 and notes that individual skills may differ. The package also contains LICENSE (the full Apache-2.0 text) and SOURCE.txt (a source and licence-basis note added by AIBars).