Overcut named in the 2026 Gartner® Innovation Insight: AI Software Factories reportRead more

Never miss a changelog

Every user-facing change ships with a changelog entry — automatically. Overcut spots UI, API, and CLI changes on each PR, drafts a properly formatted entry, and commits it once you approve.

Try it now
Auto Changelog Reminder — example generated output

Two steps, zero nagging

Overcut clones the PR branch, scans the diff for user-facing changes, and suggests a formatted changelog entry — committing it for you on approval.

Auto Changelog Reminder — how the workflow runs, trigger to result

The edge cases, covered

It knows what actually counts as user-facing and how your changelog is formatted, so the right entries land in the right file every time.

Knows what's user-facing

Flags UI, API, and CLI changes and skips internal refactors, so you're only prompted when it actually matters.

Matches your format

Follows your changelog's existing heading structure, bullet style, and categorization — nothing to reformat afterward.

Commits on approval

Suggests the entry inline and writes it to the changelog only once you give the go-ahead.

Finds the right file

Locates the relevant changelog automatically, including package-specific files in a monorepo.

Integrates with your stack

Runs on your pull requests and writes back to your repo — no new tools to adopt.

GitHub
Overcut

On by default, every PR

Triggers automatically 60 seconds after a PR opens, or on demand with /changelog on any PR.

Auto Changelog Reminder — a run timeline from a real execution

Trusted by industry leaders worldwide

Dvir Cooper

“In just four months, Overcut has saved us countless hours and quickly become an indispensable tool that developers actively request for new projects.”

Dvir Cooper,R&D Group Lead, Zesty

Read the full story

100+

hours saved in the first four months

9/10

new projects start on overcut

Your AI factory starts with one command

Book a 30-min demo call
Claude logoOpenAI logoCursor logoGitHub Copilot logo
~/acme-app
$ npx overcut init
✓ Signed in
✓ Current workspace: Acme
✓ Connected: Claude Code
> Set up Overcut for this repo.
Inspecting repo: GitHub remote, pnpm, vitest, GitHub Actions
Proposed workflows:
1. Code review
2. Fix CI
3. Auto docs update on merge
Draft run of "Code review" passed.
Publish and activate triggers? [y/N]