intl-pipeline

Operates the manifest-driven incremental translation pipeline for ethereum.org content across 24 locales.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents translation drift, manifest corruption, and runaway LLM costs when maintaining 24 translated locales of ethereum.org content, by enforcing the correct operating rules for the LLM-based intl-pipeline instead of error-prone hand-edits.

Core Features & Use Cases

  • Don't-hand-propagate enforcement: Explains when editing translated files is allowed versus when English changes must flow through the pipeline, including the stamp_only escape hatch.
  • Recovery and triage runbooks: Covers corrupted manifests, wedged intl/pending-{base} branches, bad translations, RECITATION failures, and cost-guard aborts with concrete commands.
  • Sanitizer and ETHGlossary policy: Defines the code-block-split rule for sanitizer fixes and treats ETHGlossary as the canonical source for term transliteration.
  • Use Case: A contributor updates English frontmatter and wonders whether to edit 24 locale files; the Skill directs them to dispatch intl-pipeline.yml so manifests stay in sync.

Quick Start

Ask how to safely propagate an English content change to all translated locales without breaking the translation manifests.

Frequently Asked Questions about intl-pipeline

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

FAQPage Schema
How do I propagate an English content change to all translated locales?

Trigger the intl-pipeline.yml workflow on the changed English file instead of hand-editing locale files. The pipeline incrementally translates only the changed sections across all locales and re-stamps the manifests, keeping the English-to-locale map valid.

How do I fix a corrupted translation manifest?

Delete both manifest files (source.json and translation.json) for the affected file and locale together, then re-run the pipeline. It auto-detects the missing manifests and runs a full translation to regenerate them; never hand-edit manifest JSON.

When is it safe to hand-edit a translated file?

Hand-edits are allowed only when the English source has not changed since the manifest was stamped, such as fixing a mistranslation or typo. If English moved, run the pipeline or use stamp_only after the edit to avoid desyncing the manifest.

Why did the translation run abort with a cost-guard error?

The run hit a spend bound such as the per-call prompt ceiling or the $100 run fuse. Check input tokens per call in the log; healthy runs average 4k-9k, and far higher values indicate a batching bug rather than a budget to raise.

Should hot fixes to staging or master be translated before deploy?

No, hot fixes to staging or master go out English-only by design. The pipeline only targets dev in production, and translations catch up on the next release cycle when dev flows through prepare-release.

What should I do when a term is missing from ETHGlossary?

Do not add a local override or parallel term bank. Flag the missing term in the review report or per-language findings file so a maintainer can add it upstream in ETHGlossary, which is the canonical source for term translations.