changelog-generator

To generate release notes from conventional commits, you can parse git tag ranges, ref ranges, stdin, or input files to produce markdown or JSON changelog entries organized into Keep a Changelog sections.

Yes, you can validate commit subjects against Conventional Commits rules to enforce commit-message linting, allowing your CI pipeline to fail automatically when invalid messages are detected.

Semantic versioning bump detection analyzes conventional commit histories to identify major, minor, or patch changes, automatically categorizing release entries into Keep a Changelog ordered sections.

The best way to prepend a changelog entry to CHANGELOG.md is by using safe prepend-to-file behavior, which inserts the newly generated markdown release draft without rewriting existing file history.

Yes, changelog generation supports monorepo releases and pull request validation by accepting diverse inputs like git ranges, refs, stdin, and file-based inputs for CI checks.

Yes, you can output changelog entries in either JSON or markdown format, enabling automated processing of release notes or direct human-readable documentation drafting.