<-Back to All Articles
Ditto: From draft to deploy.
Now in Beta: Your style guide should review every pull request

Ditto's PR Review Bot checks every pull request against your style guide — so no text ships without a content review.

Product copy is getting built outside of linear workflows now. Engineers and PMs are generating feature prototypes directly in code with tools like Claude Code, shipping them into a pull request, and pushing straight to production. The traditional loop — write copy in a doc, design it in Figma, hand it off to engineering — is collapsing. That's a good thing for speed. It's a dangerous thing for consistency.

When new text enters your codebase this fast, review becomes either a bottleneck or something that gets skipped entirely. And when it gets skipped, that's how you end up with three different versions of the same error message in production.

Ditto has always helped teams govern their product copy — from draft to design to development. But as more work moves directly into code, your style guide needs to meet your team where the text is actually changing: in your pull requests.

That's why we built the Ditto PR Review Bot.

Ditto's PR review bot in action.

What It Does

Ditto's PR Review Bot plugs directly into your team's GitHub workflow. When a pull request is opened, the bot scans it for user-facing text and checks it against the guidelines and copy you've already established in Ditto.

It does two things:

Checks text against your style guide. The bot evaluates new and modified strings against your team's style guide rules in Ditto and surfaces inline suggestions — right in the PR diff — on how to edit the text to match your guidelines. Each suggestion includes the rationale behind it, so reviewers understand which rule was applied and why.

Surfaces opportunities for reuse. If your team already has an approved version of similar text in Ditto, the bot will flag it and suggest using the existing copy instead. No more accidentally creating a fourth variation of "Something went wrong. Please try again."

You can accept the suggestions directly, or use it as a starting point for further review. Accepting a suggestion commits the change directly to the branch — no extra steps.

How to Trigger It

You have two options:

  • Tag-based: Configure a GitHub label (like ditto) that automatically triggers the bot whenever it's applied to a PR.
  • On-demand: Comment /ditto review in any pull request to have the bot review the PR on the spot.

Why This Matters

Nothing slips through the cracks. Every PR gets checked, whether your content designer is available to review it or not. The bot provides a consistent baseline of quality for all user-facing text entering production.

Your content design function scales. As your team's shipping velocity increases, human reviewers are no longer the bottleneck. The bot handles the first pass, so content designers can focus on the work that requires human judgment — and trust that the rest is covered.

Join the Beta

The PR Review Bot is currently in beta, and we're looking for teams to try it out and help us shape the feature.

Getting set up is straightforward — all you'll need to do is install the Ditto GitHub App on your team's repository. We'll handle the rest.

Book a call to get started →

We want your feedback. As a beta tester, you'll have a direct line to our team to tell us where the bot is working, where it's not, and what you'd want it to do next. Your input will shape what we ship.