From merge to docs ticket, automatically

When a PR merges to main, Overcut clones the product and docs repos, has a developer agent flag the user-facing changes, and lets a tech writer agent plan and open one cohesive issue per feature — then comments back on the PR with links.

The edge cases, covered

It only files docs work that actually matters, groups it sensibly, and never duplicates an issue you already have open.

Filters for customer impact

Skips internal-only PRs — APIs, schemas, env vars, refactors — and only raises docs work for changes users will actually notice.

Groups by feature, not files

Organizes documentation around logical feature areas and merges complementary changes into a single cohesive ticket.

Avoids duplicate issues

Checks existing open needs-docs-update issues before creating anything, so the same gap is never filed twice.

Conflict-aware splitting

Keeps changes that touch the same doc files together and only separates truly independent features, preventing merge clashes downstream.

Closes the loop on the PR

Comments back on the original product PR with links to every doc issue, or a clear note when no documentation is needed.

Plugged into your repos and tracker

Reads code straight from your product repository and writes structured issues into the project linked to your docs repo, wherever your team tracks work.

Running from day one

Fires automatically when a pull request merges to main, or on demand with the /update-docs command on any merged PR.