writing-proofreading

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Writing Proofreading

文章审校助手，提供 6 步审校流程，帮助打磨中文文章。

This is a writing proofreading assistant that provides a 6-step proofreading process to polish Chinese articles.

Prerequisites

Tool	Type	Required	Install
markdownlint-cli2	cli	No	`npx markdownlint-cli2` (no install needed, used in step 6)
markdown-lint	skill	No	Included in `npx skills add niracler/skill` (for repo setup)

Do NOT proactively verify these tools on skill load. If a command fails due to a missing tool, directly guide the user through installation and configuration step by step.

Tool	Type	Required	Install
markdownlint-cli2	cli	No	`npx markdownlint-cli2` (no install needed, used in step 6)
markdown-lint	skill	No	Included in `npx skills add niracler/skill` (for repo setup)

Do NOT proactively verify these tools on skill load. If a command fails due to a missing tool, directly guide the user through installation and configuration step by step.

核心原则

Core Principles

原则	说明
先讨论再修改	提出方案让用户选择，不直接动手
分段审校	按 Markdown 标题为节点，每次 1-2 个标题
启发式提问	对草稿内容用提问引导，不替用户决定

Principle	Description
Discuss before revising	Propose solutions for the user to choose from; do not make changes directly
Segmented proofreading	Use Markdown headings as nodes, handle 1-2 headings at a time
Heuristic questioning	Guide the user with questions about the draft content; do not make decisions on their behalf

6 步审校流程

6-Step Proofreading Process

text

1. 结构诊断 → 2. 读者 Context → 3. 语言规范 → 4. 信源查证 → 5. 风格检查 → 6. Markdown 格式

text

1. Structure Diagnosis → 2. Reader Context Check → 3. Language Standards → 4. Source Verification → 5. Style Consistency Check → 6. Markdown Formatting

步骤 1: 结构诊断

Step 1: Structure Diagnosis

目标：确保文章结构清晰、主题明确

拆解段落，识别主题
提出 2-3 个重组方案，先讨论再修改
删除内容移到「素材.md」保留

详见 structure-review.md

Goal: Ensure the article has a clear structure and definite theme

Break down paragraphs and identify themes
Propose 2-3 restructuring options, discuss before revising
Move deleted content to "materials.md" for retention

See structure-review.md

步骤 2: 读者 Context 检查

Step 2: Reader Context Check

核心问题：「读者看这里会不会不明所以？」

检查项	问题表现	改进方式
背景假设	直接使用专有名词、缩写	补充解释或脚注
自说自话	「就是那种...」但没说清楚	具体化描述
跳跃逻辑	从 A 直接到 C	补充过渡说明
隐含情绪	「实在是太...」但没铺垫	先铺垫原因
信息差	假设读者知道来龙去脉	简要交代背景

详见 structure-review.md

Core Question: "Will readers find this confusing?"

Check Item	Problem Performance	Improvement Method
Background assumptions	Direct use of proper nouns or abbreviations	Add explanations or footnotes
Self-centered expression	Phrases like "you know that kind of..." without clear elaboration	Provide specific descriptions
Jumping logic	Directly transitioning from A to C	Add transitional explanations
Implied emotions	Phrases like "it's just so..." without prior context setting	First lay out the reasons
Information gap	Assuming readers know the full context	Briefly explain the background

See structure-review.md

步骤 3: 语言规范

Step 3: Language Standards

基于余光中《怎样改进英式中文》：

问题	示例
抽象名词做主语	❌ 收入减少改变生活 → ✅ 他因收入减少而改变生活
冗赘句式	❌ 基于这个原因 → ✅ 因此
动词弱化	❌ 作出贡献 → ✅ 贡献
介词/连接词堆砌	减少「有关」「和」「以及」
被动语态滥用	❌ 问题被解决了 → ✅ 问题解决了

详见 chinese-style.md

Based on Yu Guangzhong's How to Improve British-style Chinese:

Problem	Example
Abstract nouns as subjects	❌ Reduced income changes life → ✅ He changed his life due to reduced income
Redundant sentence structures	❌ Based on this reason → ✅ Therefore
Weakened verbs	❌ Make a contribution → ✅ Contribute
Preposition/conjunction overuse	Reduce use of "related to", "and", "as well as"
Passive voice overuse	❌ The problem was solved → ✅ The problem has been solved

See chinese-style.md

步骤 4: 信源查证

Step 4: Source Verification

信源优先级：政府官方 > 权威媒体 > 行业媒体 > 避免个人博客

数据使用原则：

不能只扔数据，要融入体验
体感判断需要脚注支撑推算逻辑
科普精简，详细放脚注

工作节奏：查一个 → 讨论 → 写一个 → 确认 → 下一个

详见 source-verification.md

Source Priority: Government official sources > Authoritative media > Industry media > Avoid personal blogs

Data usage principles:

Do not just present data; integrate it with experience
Sensory judgments need footnotes to support the reasoning logic
Keep popular science content concise; place details in footnotes

Work Rhythm: Check one → Discuss → Write one → Confirm → Next one

See source-verification.md

步骤 5: 风格一致性

Step 5: Style Consistency

检查是否符合个人写作风格：

检查项	说明
标志性表达	「怎么说呢」「其实」「有点...」
语气特征	自嘲式开场、括号补充吐槽
量化习惯	用具体数字增强说服力
加粗克制	每标题下 ≤ 3 处

避免：

「不是……而是……」句型（AI 味）
加引号的「幽默」比喻
emoji 或序号开头
频繁使用破折号

详见 personal-style.md

Check if it aligns with personal writing style:

Check Item	Description
Signature expressions	Phrases like "how to put it", "actually", "a bit..."
Tone characteristics	Self-deprecating opening, parenthetical comments/jokes
Quantification habits	Use specific numbers to enhance persuasiveness
Restrained bolding	≤3 uses per heading

Avoid:

Sentence structure "not...but..." (has AI-like tone)
"Humorous" metaphors in quotation marks
Opening with emojis or numbers
Frequent use of em dashes

See personal-style.md

步骤 6: Markdown 格式化

Step 6: Markdown Formatting

自动化格式检查（需仓库已配置 markdown-lint skill）：

bash

npx markdownlint-cli2 article.md          # 检查
npx markdownlint-cli2 --fix article.md    # 自动修复

仓库未配置？使用 markdown-lint skill 完成初始化。

自动化工具无法覆盖的内容审查：

标题层级是否合理（H2→H3，不跳级）
列表格式是否一致（全用
```
-
```
或全用
```
*
```
）
代码块是否正确标记语言

Automated format check (requires markdown-lint skill configured in the repository):

bash

npx markdownlint-cli2 article.md          # Check
npx markdownlint-cli2 --fix article.md    # Auto-fix

Repository not configured? Use the markdown-lint skill to complete initialization.

Content review not covered by automated tools:

Whether heading levels are reasonable (H2→H3, no skipping levels)
Whether list formats are consistent (use all
```
-
```
or all
```
*
```
)
Whether code blocks are correctly labeled with languages

Review 节奏

Review Rhythm

text

┌─────────────────────────────────────────────────┐
│  每个标题下的审校流程                             │
│                                                 │
│  1. 读取当前段落                                 │
│  2. 按 6 步流程检查                              │
│  3. 提出修改建议（不直接改）                      │
│  4. 等待用户确认                                 │
│  5. 确认后再处理下一个标题                        │
└─────────────────────────────────────────────────┘

关键：每段 review 后等待确认，不连续处理多个段落。

text

┌─────────────────────────────────────────────────┐
│  Proofreading process for each heading          │
│                                                 │
│  1. Read the current paragraph                  │
│  2. Check according to the 6-step process       │
│  3. Propose revision suggestions (no direct changes) │
│  4. Wait for user confirmation                  │
│  5. Process the next heading after confirmation │
└─────────────────────────────────────────────────┘

Key: Wait for confirmation after proofreading each section; do not process multiple sections consecutively.

写作风格速查

Quick Reference for Writing Style

要素	要求
语言	口语化，像和朋友聊天
段落	一个段落一个主题
加粗	只在重要转折/感悟处使用，每标题下 ≤ 3 处
数据	融入体验，脚注放详细来源
坦诚	承认不足、标注未完成，保留思考痕迹

Element	Requirement
Language	Colloquial, like chatting with a friend
Paragraphs	One theme per paragraph
Bolding	Use only at important transitions/insights, ≤3 uses per heading
Data	Integrate with experience; place detailed sources in footnotes
Candor	Acknowledge shortcomings, mark unfinished content, retain thinking traces

详细参考

Detailed References

chinese-style.md - 中文语言规范
structure-review.md - 结构诊断与读者 Context
source-verification.md - 信源查证与脚注
personal-style.md - 个人风格指南

chinese-style.md - Chinese Language Standards
structure-review.md - Structure Diagnosis and Reader Context
source-verification.md - Source Verification and Footnotes
personal-style.md - Personal Style Guide