Chinese Copywriting Linter

Chinese Copywriting Linter

A skill to check and auto-correct Chinese typesetting and copywriting style violations in Markdown files, based on the Chinese Copywriting Guidelines.

When to use

Use this skill when you need to:

• Check for styling issues in Chinese .md files.
• Automatically format and correct Chinese writing files (spacing, punctuation, capitalization).
• Ensure consistency in mixed Chinese-English text.

Core Rules enforced by the Linter

1. Spacing (空格):

• Must have a space between CJK characters and Latin/numeric characters.
• Must have a space between numbers and units (e.g., 10 Gbps).
• Must not have a space between numbers and degree/percentage symbols (e.g., 90°, 15%).
• Must not have spaces before or after fullwidth punctuation in Chinese text.
• Must have a space before and after range tilde ~ (e.g., 50 Hz ~ 8000 Hz).

1. Punctuation (标点):

• Must use fullwidth punctuation in Chinese text (e.g. ！, ，, ？).
• Must not duplicate punctuation (e.g. avoid ！！, ？？).
• Must use halfwidth punctuation within pure English phrases or code snippets.
• Must use Chinese corner brackets 「 and 」 instead of Chinese double quotation marks “ and ” for first-level quotes (e.g., replace “检查” with 「检查」), and double corner brackets 『 and 』 instead of single quotation marks ‘ and ’ for nested quotes (e.g., replace ‘检查’ with 『检查』).

1. Numbers (数字):

• Must use halfwidth numbers (e.g. 1234 instead of １２３４).

1. Casing (大小写):

• Proper capitalization of technology names (e.g. GitHub, TypeScript, JavaScript, Next.js, React, HTML5, CSS3, VS Code, Node.js, iPhone, MacBook, iPad, LeanCloud).

How to execute the Linter

This skill includes a Python script linter.py located in the scripts/ directory of the skill.

1. Run in linting (dry-run) mode

To scan a file or directory for style violations without modifying the content, run:

python3 /scripts/linter.py 

2. Run in auto-fix mode

To automatically fix all solvable violations directly in the source file:

python3 /scripts/linter.py --fix 

User Communication

After executing the linter, report the findings clearly:

• If issues were found and fixed, show the count of total issues fixed and highlight a few key examples.
• If run in check-only mode, display a detailed report of line numbers, columns, and what violations occurred.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: hankunpeng
• Source: hankunpeng/skills
• License: MIT

Install and usage instructions live in the source repository linked above.