River
Y CombinatorBacked by Y Combinator

TechnicalFree tool

Generate commit messages

Describe your change or paste the diff, and get a Conventional Commits message with a clear summary line and a body that explains why.

Helpful to include

Free to start · Opens in your River workspace, ready to edit and share

Conventional Commits Format

Conventional Commits standard uses format: type(scope): description. Common types: feat (new feature), fix (bug fix), docs (documentation), style (formatting), refactor (code restructure), test (tests), chore (maintenance). This format enables automated changelogs and semantic versioning.

How It Works

River's Commit Message Generator creates well-formatted commit messages following Conventional Commits standard. You describe changes, and the AI writes clear messages with proper type prefixes, scope, and descriptions. Perfect for maintaining clean git history and enabling automated changelog generation.

Unlike vague commit messages, we follow best practices. The AI understands Conventional Commits format (feat, fix, chore, etc.), writes clear descriptions, and structures messages for both humans and automation tools.

This tool is perfect for developers maintaining projects, teams standardizing commits, open-source contributors following conventions, and projects using semantic versioning.

  1. Describe changes

    Explain what you changed

  2. AI generates message

    Creates formatted commit message

  3. Copy and commit

    Use in git commit command

What You Get

  • Conventional Commits format message
  • Proper type prefix (feat, fix, etc.)
  • Clear, concise description
  • Optional scope and body
  • Ready to commit

Common questions

How do you write a good commit message?

Write a good commit message with a short imperative summary line (about 50 characters, e.g. "fix: handle null user in checkout"), a blank line, and a body that explains what changed and why rather than how. Use the Conventional Commits format (type: description) for consistency, keep one logical change per commit, and reference related issues where relevant.

What is the ideal commit message format?

A widely used format is Conventional Commits: a type prefix (feat, fix, docs, refactor, test, chore), an optional scope in parentheses, and a concise imperative description - for example "feat(auth): add password reset flow." An optional body and footer can add detail or reference issues, which keeps history readable and enables automated changelogs and versioning.

What's Conventional Commits?

A specification for commit message format. Uses type prefixes (feat:, fix:, etc.) to categorize changes. Enables automated changelog generation and semantic versioning. Widely adopted in open source.

When should I use feat vs fix?

Use feat: for new features or capabilities. Use fix: for bug fixes. feat: increments minor version. fix: increments patch version. This matters for semantic versioning.

Should every commit be a single type?

Yes, ideally. If commit does multiple things (adds feature AND fixes bug), consider splitting into separate commits. Atomic commits with single purpose create clearer history and easier reverts.

Built by

Chandler Supple

Co-founder & CEO, River

Chandler has spent the last six years working in AI, building tools for millions of users and Fortune 100 companies. In 2025, he co-founded River to build a new kind of operating system for AI agents.

Reviewed by

Brian Joseff, Co-founder, River