Lexeri CLI: Check terminology automatically in your CI/CD pipeline

Consistent terminology plays a big part in how clear and professional your software feels – in the user interface, in the documentation, and in every translation. That's exactly where our new tool comes in: the Lexeri Check CLI brings terminology checks straight into your automated build and CI/CD processes. It's available on npm now.

Check terminology without having to think about it

Terms creep in quickly: sometimes it's "whitelist", sometimes "allowlist", sometimes "login", sometimes "sign-in". In UI text, release notes, and translated strings, this often only surfaces late – if at all. Manual checks help, but they're easy to forget in day-to-day work.

The Check CLI automates this step. It checks your files against your Lexeri termbase and reports every non-preferred term – automatically, on every commit or merge request. This makes terminology a fixed part of your quality assurance, instead of a task you have to remember.

 

Getting started is simple

The CLI needs only Node.js and an API token – no editor, no extra infrastructure. A single command is enough:

 

npx @lexeri/check-cli --locale en src/i18n/en.json

 

The CLI uploads the file, runs the term check, lists the matches clearly, and exits with a meaningful exit code. If it finds non-preferred terminology, the build fails – so nothing unchecked makes it into your release.

 

Fits the tools your team already uses

Because the Check CLI runs on the command line, it slots neatly into existing pipelines – for example, GitLab CI. You store your token as a masked variable, add a few lines to your pipeline configuration, and the check runs automatically with every change. On request, the CLI produces a machine-readable JSON report that you can save as an artifact or process further.

 

From UI strings to translations

Terminology isn't just in your source code. The Check CLI checks a wide range of formats:

  • String resources like JSON, RESX, .properties, .strings, YAML, or PO
  • Translation formats like XLIFF – here you can additionally check the translation against its target language
  • Documentation in Markdown, HTML, or as subtitles
  • Office and DTP documents like Word, Excel, PowerPoint, or PDF

This way, you keep your terms consistent across all your content – from the first line of source code to the finished translation.

 

The perfect counterpart to the VS Code extension

The Check CLI complements our Visual Studio Code Extension: while the extension is made for interactive checks as you write, the CLI takes over automated control in the pipeline. Together, they cover the entire development process – from editing in the editor to automated quality assurance before release.

 

Try it now

The Lexeri Check CLI is available now:

Create an API token directly in the Lexeri web UI. Questions or feedback? Write to us at info@lexeri.com – we'd love to hear from you!