intl-review

Reviews ethereum.org translation PRs against ETHGlossary terminology and MDX integrity rules.

6.0k|5.4k|Updated Jan 6, 2018
One-click install
npx skills add https://github.com/ethereum/ethereum-org-website --skill intl-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: intl-review
Source: https://github.com/ethereum/ethereum-org-website/tree/main/.claude/skills/intl-review
Command: npx skills add https://github.com/ethereum/ethereum-org-website --skill intl-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reviewing machine-translated content across 24 languages is error-prone: brand names get mistranslated, internal links get localized and break navigation, MDX syntax errors break builds, and semantic inversions (like swapping proof-of-stake and proof-of-work) slip through. This Skill provides a deterministic review framework so every translation PR is evaluated against the same authoritative rules.

Core Features & Use Cases

  • ETHGlossary-as-authority enforcement: Verifies every translated term against the ETHGlossary API, classifying deviations as critical issues that can be auto-fixed.
  • Severity triage and scoring: Distinguishes critical (build-breaking, navigation-breaking, semantic) issues from warnings, and scores each locale on a 5-category rubric (Brand Name Preservation, Technical Accuracy, Semantic Fidelity, Terminology Consistency, Tone/Register).
  • Multi-agent review roles: Splits large PR reviews across structural, terminology, and semantic agents, with per-language rules for 13 non-Latin-script languages.
  • Use Case: When reviewing a Japanese translation PR on an intl/pending-dev branch, the Skill checks that Solidity stays Latin per its always_latin rule, flags a translated /governance href as critical, and produces a per-language quality score plus findings file update.

Quick Start

Review the Korean translations on the intl/pending-dev branch and report critical issues with a quality score.

Frequently Asked Questions about intl-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review translation PRs for ethereum.org?

Run the /review-translations slash command against the intl/pending-* branch. The review verifies terms against ETHGlossary, checks MDX syntax and internal hrefs, applies auto-fixes by default, and produces a per-language quality score report.

What counts as a critical issue in translation review?

Critical issues are build-breaking MDX syntax errors, translated internal hrefs, semantic inversions like proof-of-stake/proof-of-work swaps, and deviations from ETHGlossary entries with deterministic script rules. These are auto-fixed unless --no-fix is passed.

Should translated frontmatter tags be reverted to English?

No. Brand-name tags like solidity or hardhat must stay English, but concept tags like smart contracts or testing are intentionally translated by the pipeline. Reverting a translated concept tag to English is itself a critical error.

How is translation quality scored across languages?

Each locale is scored 0-10 on five categories: Brand Name Preservation, Technical Accuracy, Semantic Fidelity, Terminology Consistency, and Tone/Register. The overall score is the average of the five, reported separately from the critical-issue list.

When should tone inconsistency block a translation merge?

Never directly. Tone and register shifts (like German du/Sie mixing) are warnings, not criticals, because the right register is judgment-based. They are flagged for native-speaker review and affect the Tone/Register score but do not block merge.

What happens if a term is missing from ETHGlossary?

Missing terms are flagged in the review report and noted in the per-language findings file for upstream addition. Reviewers must not patch the locale or invent terminology; the script-aware fallback (transliterate for non-Latin scripts, keep Latin otherwise) applies.