fix-crowdin-pr

Fix coderabbit review findings on Crowdin translation PRs and sync corrections back to Crowdin.

5.2k|553|Updated Jan 27, 2015
One-click install
npx skills add https://github.com/lukevella/rallly --skill fix-crowdin-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-crowdin-pr
Source: https://github.com/lukevella/rallly/tree/main/.claude/skills/fix-crowdin-pr
Command: npx skills add https://github.com/lukevella/rallly --skill fix-crowdin-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @crowdin/cli.

What problem does it solve?

Crowdin force-pushes the l10n_main branch on every sync, so translation fixes applied only to the PR branch get overwritten. This Skill resolves coderabbit review findings on Crowdin translation PRs in a way that survives the next sync by uploading corrections to Crowdin first, then pushing identical changes to the branch.

Core Features & Use Cases

  • Review Triage: Fetches coderabbit comments from the open "🌐 New Crowdin updates" PR (or a given PR number) and judges each finding against the English source locales.
  • Dual-Sync Fixes: Applies exact string replacements to locale JSON files, uploads corrections to Crowdin via the Crowdin CLI or REST API, then commits and pushes to l10n_main.
  • Thread Management: Replies to and resolves every review thread via the GitHub API, citing the fix commit or explaining skipped findings.
  • Use Case: A maintainer sees coderabbit flagged mistranslations on the weekly Crowdin sync PR; this Skill applies the valid fixes, syncs them to Crowdin so they persist, and closes out all review threads.

Quick Start

Fix the coderabbit findings on the open Crowdin translation PR and sync the corrections back to Crowdin.

Frequently Asked Questions about fix-crowdin-pr

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

FAQPage Schema
How do I fix coderabbit findings on a Crowdin translation PR?

Fetch the PR review comments with the GitHub API, filter to coderabbitai, and judge each finding against the English source locales. Apply accepted fixes with exact string replacement, upload them to Crowdin first, then push identical changes to the l10n_main branch.

Why must Crowdin translation fixes be uploaded to Crowdin before pushing to the branch?

Crowdin force-pushes l10n_main on every sync, so a fix that lands only on the PR branch gets overwritten. Uploading corrections to Crowdin first ensures the next sync exports identical content and the branch stays stable.

How do I upload corrected translations to Crowdin from the command line?

Use the Crowdin CLI with npx @crowdin/cli upload translations -b main -l <language-id> --auto-approve-imported, passing the token and project id as environment variables. A REST API fallback using storages and translations endpoints works when the CLI is unavailable.

How do I resolve GitHub review threads programmatically?

Reply to comments with gh api POST to the pulls comments replies endpoint, then resolve threads via GraphQL. Query reviewThreads to get thread ids and call the resolveReviewThread mutation for threads still open.

What are the limitations of auto-approving translation fixes into Crowdin?

Auto-approved imports displace existing human translations, so wrong fixes cause real damage. Findings on languages you cannot judge should be skipped rather than guessed, and anything contradicting the English source should be rejected.