tc-review

Detect Simplified Chinese characters and Mainland-specific vocabulary in Traditional Chinese writing.

Updated May 18, 2026
One-click install
npx skills add https://github.com/solitude6060/Yao-skills --skill tc-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tc-review
Source: https://github.com/solitude6060/Yao-skills/tree/main/skills/tc-review
Command: npx skills add https://github.com/solitude6060/Yao-skills --skill tc-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

tc-review prevents accidentally publishing Traditional Chinese content that contains Simplified character leaks, Mainland-specific phrasing, awkward translationese, or unnecessary English insertion.

Core Features & Use Cases

  • Simplified Chinese leak detection: Flags both direct Simplified characters and Mainland construction patterns, prompting a full-paragraph recheck rather than a one-off fix.
  • Taiwan engineer fluency enforcement: Improves sentence flow to sound like technical writing used in Taiwan, while preserving technical precision.
  • Controlled English/term handling: Keeps English identifiers, commands, paths, API names, and technical terms unchanged, while reducing inappropriate “ordinary English word” insertions.
  • Context-aware output mode: Provides silent self-correction when reviewing your own output, and localized issue lists (e.g., with positions/line references) when reviewing files or others’ documents.

Quick Start

Ask tc-review to review your Traditional Chinese text for Taiwan-appropriate wording and any Simplified/alternative Mainland phrasing before you publish it.

Frequently Asked Questions about tc-review

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

FAQPage Schema
How do I detect Simplified Chinese character leaks in Traditional Chinese documentation?

To detect Simplified Chinese character leaks in Traditional Chinese documentation, you can run a pre-publication review that flags direct Simplified characters and Mainland-specific phrasing while preserving technical terms and identifiers.

What is the best way to check Traditional Chinese text for Taiwan engineer fluency?

The best way to check Traditional Chinese text for Taiwan engineer fluency is to enforce sentence naturalness during the review process, minimizing improper English insertions and awkward translationese while maintaining technical precision.

Can I review code documentation for Mainland-specific vocabulary without altering API names and paths?

Yes, you can review code documentation for Mainland-specific vocabulary without altering API names and paths, because the review process explicitly preserves all technical constraints, identifiers, commands, and file paths.

Does pre-publication review for Traditional Chinese content provide localized issue lists with line references?

Pre-publication review for Traditional Chinese content does provide localized issue lists with positions or line references when reviewing files or others' documents, while offering silent self-correction for your own chat replies.

Why does my Traditional Chinese writing contain awkward translationese and unnecessary English insertion?

Traditional Chinese writing contains awkward translationese and unnecessary English insertion when sentence flow is not properly localized, requiring a fluency enforcement check to reduce inappropriate ordinary English words while keeping technical terms intact.

When do I need a Simplified Chinese leak detection check for my Traditional Chinese content?

You need a Simplified Chinese leak detection check for your Traditional Chinese content during any pre-publication check for 繁中-facing material, including chat replies, README files, plan documents, and review documents.