Does this skill run tests?

Yes, as part of its workflow, it runs 'composer test' to ensure that the updated locale files do not cause any regressions in the application.

What files does this skill modify?

The skill primarily manages and updates JSON files located within the lang/ directory of the JournalOS repository.

Will it break my variable placeholders?

No, the skill is explicitly instructed to preserve tokens such as :count, :name, or {value} and will not alter embedded HTML or Markdown.

Does it automatically translate the text?

It identifies missing or empty keys and suggests appropriate translations based on context and existing patterns, then validates them against the project's standards.

How does it ensure the JSON remains valid?

The skill includes a validation step to check JSON correctness, consistent indentation, and the absence of duplicate keys before finalizing changes.

JournalOS Translations Updater

Name: JournalOS Translations Updater
Author: djaiss

bydjaiss

•

Content Management

Automates the synchronization and completion of JournalOS localization files to ensure a consistent multilingual user experience.

About

The JournalOS Translations Updater skill streamlines the localization process by automatically identifying and fixing missing or invalid translation keys across the project. It leverages the project's internal command structure to regenerate locale files from the source code and applies a systematic approach to filling in empty strings while strictly preserving critical placeholders and formatting tokens. This skill is essential for maintaining UI consistency whenever new modules are added or existing copy is modified, ensuring that all supported languages remain in sync and functional.

Key Features

Intelligent scanning for missing, null, or empty JSON entries
JSON syntax validation and formatting consistency
Strict preservation of tokens and placeholders like :name and {value}
Integration with the project test suite for quality assurance
Automated locale regeneration using composer commands
1 GitHub stars

Use Cases

Standardizing tone and terminology across multiple locale files
Audit and repair of incomplete translation files containing empty values
Synchronizing language files after introducing new UI strings or modules

About

Key Features

Intelligent scanning for missing, null, or empty JSON entries
JSON syntax validation and formatting consistency
Strict preservation of tokens and placeholders like :name and {value}
Integration with the project test suite for quality assurance
Automated locale regeneration using composer commands
1 GitHub stars

Use Cases

Standardizing tone and terminology across multiple locale files
Audit and repair of incomplete translation files containing empty values
Synchronizing language files after introducing new UI strings or modules