change-logger

Automatically generate a changelog by running a script that reads your current git state and writes dated, readable entries to CHANGELOG.md. It groups changes by path segments and applies a base marker to track progress without re-listing old commits.

Yes, you can generate release notes for a specific commit range like main..HEAD. The script processes commits within your specified range or staged-only changes, grouping them into concise, analogy-rich entries for your changelog.

Keep a changelog human-friendly by generating analogy-rich entries grouped by path segments. This format translates raw git state into readable notes, making it ideal for PRs, release notes, and team communications.

The base marker tracks your changelog progress by recording the last processed commit. It prevents the script from re-listing old commits on subsequent runs, ensuring CHANGELOG.md only appends new, dated entries from the current git state.

Yes, the changelog generator works with staged-only changes. You can configure the script to process only staged files instead of the full commit range, capturing immediate working directory updates for your release notes.

An analogy-rich format makes changelog entries beginner-friendly and highly readable. By grouping git changes by path segments with concise analogies, the generated CHANGELOG.md communicates technical updates clearly for PRs and team updates.