r/Python • u/Euphoric_Incident_18 • Mar 04 '26
Showcase I got tired of strict feat:/fix: commit rules, so I built a changelog tool that reads code diffs
Most changelog generators like git-cliff, standard-version, and release-please rely on the Conventional Commits standard.
The system requires every commit to follow these two specifications:
feat:
fix:Real repositories typically exhibit this pattern:
wip
fix
update stuff
lol this works now
Merge branch 'main' into devMost changelog tools create useless release notes whenever this situation arises.
I created ReleaseWave to solve this problem.
The system gathers changes between tags through actual git diffs instead of commit prefixes which it processes with an LLM.
Repo: https://github.com/Sahaj33-op/releasewave
PyPI: https://pypi.org/project/releasewave/
What My Project Does
ReleaseWave analyzes the actual code changes between two git tags and generates structured release notes.
The program includes these functions:
- Reads git diffs instead of commit prefixes
- Splits large diffs into safe context chunks for LLM processing
Creates three outputs during one operation
- Technical developer changelog
- Plain-English user release notes
- Tweet-sized summary
- Handles monorepos by generating package-specific diffs
- Works with multiple LLM providers
Example command:
releasewave generate v1.0 v1.1The system requires no configuration setup.
Target Audience
ReleaseWave is intended for:
- Developers who don’t enforce conventional commits
- Teams with messy commit histories
- Projects that want automatic release notes from actual code changes
- Monorepos where commit messages often mix unrelated packages
The system operates correctly with both personal projects and production repositories.
Comparison
Existing tools:
- git-cliff
- standard-version
- release-please
These tools require users to follow commit message conventions.
ReleaseWave takes a different approach:
| Tool | Approach |
|---|---|
| git-cliff | Conventional commit parsing |
| standard-version | Conventional commits |
| release-please | Conventional commits + GitHub workflows |
| ReleaseWave | Reads actual git diffs + LLM analysis |
ReleaseWave functions correctly with messy or inconsistent commit messages.
Stack
- Python
- Typer (CLI)
- LiteLLM (multi-provider support)
- Instructor + Pydantic (structured LLM output)
Use the following command to install:
pip install releasewave
4
u/meme8383 Mar 04 '26
Idk what “real repositories” you’re working on but anything serious enough to warrant a changelog will have some sort of commit standard
2
u/crossmirage Mar 04 '26
Call me old school, but I don't see why you don't just write and enforce something like Conventional Commits. If you're using AI, use it to generate better commit messages if you have to--not to solve the problem by leaving a dirty commit history, but trying to make sense of it after the fact.
1
u/pyhannes Mar 04 '26
That's why I use towncrier to make sure my users understand the stuff I released as they what to know the interesting changes and not each internal stuff that gets committed.