mcpField
L
lovstudio:translation-review

lovstudio:translation-review

github.com/lovstudioDocuments7341 installsUpdated 1d ago
Repository

About lovstudio:translation-review

lovstudio:translation-review is a skill for systematically reviewing English translations against Chinese source documents. It checks six dimensions, prioritizes findings, and reports source-document issues separately.

Key features

  1. 01Review translations across six dimensions
  2. 02Identify mistranslations, omissions, and additions
  3. 03Check terminology, grammar, and consistency
  4. 04Separate source issues and assign severity
  5. 05Generate and save structured review reports

Use cases

  1. 01Review an English translation against Chinese source text
  2. 02Check citations and references in academic papers
  3. 03Verify terminology in medical or technical documents
  4. 04Organize and save prioritized review findings

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/lovstudio/skills --skill lovstudio:translation-review

After installing, type/lovstudio:translation-reviewin Claude Code to confirm it loaded.

Bundled filesREADME.md

Details

From the project README

translation-review — Chinese-English Translation Review

Systematically compare a Chinese source document against its English translation, identify issues across 6 dimensions, and produce a prioritized review report.

When to Use

  • User provides a Chinese original + English translation pair for review
  • User asks to check/proofread an English translation from Chinese
  • User mentions "翻译检查", "审校", "translation review"

Workflow (MANDATORY)

You MUST follow these steps in order:

Step 1: Collect Input

Use AskUserQuestion to confirm before starting:

Ask the user:

  1. Document type — academic paper (SCI/EI), technical docs, business docs, general
  2. Domain — medicine, CS, law, finance, general (affects terminology checking)
  3. Focus areas — terminology accuracy, grammar, style, references, all (multi-select)

If the user has already provided context (e.g., "SCI 4区医学论文"), skip the obvious questions.

Step 2: Read Both Documents

Read the Chinese source and English translation. For .docx files:

pandoc "<chinese_file>.docx" -t plain --wrap=none
pandoc "<english_file>.docx" -t plain --wrap=none

For .md or .txt files, read directly.

If files are large, read in sections (offset/limit) to stay within context.

Step 3: Systematic Review

Compare the two documents across 6 dimensions, in this order:

D1: Mistranslation (meaning changed)
  • Words/phrases translated to a different meaning
  • Omissions (content in Chinese missing from English)
  • Additions (content in English not in Chinese)
  • Pay special attention to domain-specific terms that have been incorrectly generalized or specialized
D2: Terminology Accuracy
  • Domain-specific terms: check against standard English terminology
  • Abbreviation consistency: first occurrence should have full form + abbreviation
  • Proper nouns: names, institutions, gene/protein names, drug names
  • Units and measurements
D3: Grammar & Syntax
  • Subject-verb agreement
  • Tense consistency (especially in Methods vs Results)
  • Article usage (a/an/the) — common error in Chinese-to-English
  • Dangling modifiers, run-on sentences
  • Passive voice overuse
D4: Consistency
  • Same Chinese term translated differently in different places
  • Formatting inconsistencies (capitalization, hyphenation, number style)
  • Heading style consistency
D5: References & Citations (academic papers only)
  • Citation numbers match between Chinese and English versions
  • Reference format consistency (author names, journal abbreviations)
  • Missing author information in reference entries
  • In-text citation correctness
D6: Style & Register
  • Academic register appropriate for target journal
  • Overly verbose or literary phrasing
  • Chinese-influenced sentence structure (e.g., "through...method" patterns)
  • Paragraph length and structure
Step 4: Source Document Issues

While reviewing, also note issues in the Chinese source that the English faithfully translates but are themselves incorrect. Flag these separately.

Step 5: Generate Report

Output a structured review report with the following format:

# 翻译审校报告 / Translation Review Report

**Document**: [title]
**Reviewer**: 手工川 (AI-assisted)
**Date**: [YYYY-MM-DD]
**Domain**: [domain]
**Document type**: [type]

---

## Summary

[2-3 sentence overall assessment]

---

## A-Level Issues (Must Fix)

### A1. [Issue title]
**Location**: [section/paragraph]
**Original (CN)**: "..."
**Translation (EN)**: "..."
**Problem**: [explanation]
**Suggested fix**: → "..."

---

## B-Level Issues (Recommended)

### B1. [Issue title]
...

---

## Source Document Issues

### C1. [Issue title]
...

---

## Priority Summary

| Priority | # | Issue | Impact |
|----------|---|-------|--------|
| Must fix | A1 | ... | ... |
| ... | | | |

---

## Conclusion

[Overall quality assessment + recommended next steps]
Step 6: Save Report

Save the report to the same directory as the input files:

Filename: 手工川-translation-review-{YYYY-MM-DD}-v0.1.md

If a file with this name exists, increment the version.

Issue Severity Classification

LevelCriteriaExamples
A (Must fix)Meaning changed, factual error, or would cause rejectionMistranslation, wrong terminology, reference number mismatch
B (Recommended)Awkward but understandable, or non-standard usageVerbose phrasing, minor grammar, style inconsistency
C (Source issue)Error in Chinese original, faithfully translatedWrong terminology in Chinese, factual inaccuracy

Domain-Specific Checklists

Academic / SCI Papers
  • Abstract: structured, matches body content
  • Keywords: standard MeSH or domain terms
  • Reference numbers: sequential, match between CN/EN versions
  • Figure/table captions: translated and consistent
  • Statistical reporting: p-values, CI format
Medical / Biomedical
  • Disease names: ICD/MeSH standard
  • Gene/protein names: HUGO/UniProt standard (italics for genes)
  • Drug names: INN (International Nonproprietary Names)
  • Anatomical terms: Terminologia Anatomica standard
Technical Documentation
  • UI strings: consistent with product localization
  • Code snippets: untranslated, syntax preserved
  • API terms: match official documentation

Comments

Markdown supported