본문으로 건너뛰기
cccskills
무료GitHub에 공개

bmad-os-editorial-review-translation

Review translated documentation for content fidelity — detect injected, off-topic, or unauthorized content by comparing against the English source. Use when reviewing translation PRs or translated docs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

  • SKILL.md3.9 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Editorial Review - Translation Fidelity

Goal: Detect any material in translated documents that has no basis in the English source: injected messaging, off-topic additions, unauthorized links, or other non-faithful content.

Role: Strict translation fidelity auditor. Your only job is to verify that the translation contains nothing extra and omits nothing important from the source. Do not comment on fluency, grammar, or style. Assume suspicious until proven faithful. Legitimate rephrasing, section reordering within bounds, and minor cultural adaptations are allowed. New topics, opinions, promotions, or external agendas are not.

Inputs:

  • content (required) — Translated file(s) or PR diff
  • source_root (optional) — English source directory. Infer by stripping language code prefix if missing (e.g. zh-cn/ -> /).

PRINCIPLES

  1. Structure anchors everything. Match headings, section counts, links, images, code blocks, and frontmatter.
  2. Back-translate suspicious content. Convert suspect translation sections back to English for direct comparison.
  3. Links are critical. Any URL in translation not in source requires explanation.
  4. Omissions count. Missing source content can indicate censorship or incompleteness.
  5. Adaptation vs Injection. Cultural examples or clarifications that aid understanding = INFO. Agenda-driven changes = violation.

STEPS

Step 1: File Pairing

Map each translated file to its English source. Flag files without sources as ORPHAN.

Step 2: Structural Analysis

  • Compare all headings (flag new/missing/altered)
  • Compare section order and count
  • Inventory and compare all links and assets
  • Check frontmatter differences
  • Note sections >2x longer (language variance considered)

Step 3: Semantic Fidelity

For flagged sections:

  • Back-translate to English
  • Identify content without source equivalent
  • Scan for common injections: politics, promotions, personal commentary, hidden text, SEO, unrelated CTAs

Step 4: Classify

  • INJECTION: Clear added material serving different purpose (primary concern)
  • DRIFT: Significant meaning shift from source
  • ORPHAN: No source exists
  • OMISSION: Source content absent
  • LINK: URL discrepancies
  • INFO: Benign adaptations/translator notes

Step 5: Report

Use this exact format:

Translation Fidelity Review

Files reviewed: [N] translated vs [N] English sources Language: [detected]

Findings

INJECTION (requires immediate review)

[If none: "None found."]

[filename]

  • Section: [heading or line range]
  • Source says: [corresponding source content, summarized]
  • Translation says: [back-translated content]
  • Assessment: [why this is flagged as injection]

DRIFT (meaning divergence — verify intent)

[findings or "None found."]

ORPHAN (no source counterpart)

[findings or "None found."]

OMISSION (source content missing)

[findings or "None found."]

LINK (URL discrepancies)

[findings or "None found."]

INFO (noted, likely legitimate)

[findings or "None found."]

Summary

  • INJECTION: [count] — [CLEAN / REVIEW REQUIRED]
  • DRIFT: [count]
  • ORPHAN: [count]
  • OMISSION: [count]
  • LINK: [count]
  • INFO: [count]

If zero INJECTION and zero DRIFT findings: state "Translation appears faithful to source material."

If INJECTION findings exist: state clearly at the top: "ACTION REQUIRED: Potential content injection detected. Human review of flagged sections is strongly recommended before merge."

HALT CONDITIONS

  • No translated files identifiable
  • No English sources can be located
  • Input content empty

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Audit BMAD source files for file-reference convention violations using parallel Haiku subagents. Use when users requests an "audit file references" for a skill, workflow or task.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

bmad-code-org/bmad-utility-skills82026년 9월 25일 업데이트

Analyzes changes since last release and drafts them directly into the project's CHANGELOG.md. Use when users requests 'update the changelog' or 'prepare changelog release notes'

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

bmad-code-org/bmad-utility-skills82026년 9월 25일 업데이트

Generate social media announcements for Discord, Twitter/X, Facebook, and LinkedIn from the latest changelog entry. Use when user asks to 'create release announcement' or 'create social posts' or share changelog updates.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

bmad-code-org/bmad-utility-skills82026년 9월 25일 업데이트

Create, update, fix, or refine documentation using Diataxis framework and BMad Method style guide. Use when user asks to 'create a doc', 'update docs', 'fix docs style', 'refine docs', or 'improve docs writing'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

bmad-code-org/bmad-utility-skills82026년 9월 25일 업데이트

Orchestrate HITL triage of review findings using parallel agents. Use when the user says 'triage these findings' or 'run findings triage' or has a batch of review findings to process.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

bmad-code-org/bmad-utility-skills82026년 9월 25일 업데이트

Analyze all github issues. Use when the user says 'triage the github issues' or 'analyze open github issues'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

bmad-code-org/bmad-utility-skills82026년 9월 25일 업데이트

bmad-code-org의 스킬 모두 보기

이 스킬의 문제 신고