Guide · Agent skill
How to use the Chinese Code Review Guide agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The chinese-code-review skill is a reference guide that shapes how an AI agent writes code review comments in Chinese. It is written for Chinese-speaking developers and team leads who want reviews that are direct about bugs without sounding harsh. After this guide you will know what the skill does, how to install it, how to invoke it, and what to expect from its output.
Chinese Code Review GuidejnMetaCode/superpowers-zh · MIT Download the skill Quick start
- 1Download the ZIP. Get the chinese-code-review ZIP from the skill page on this site.
- 2Unzip the skill folder. Extract the archive so the folder containing SKILL.md is in place.
- 3Choose a location. Place it in ~/.claude/skills/ for personal use, or in a project's .claude/skills/ folder for one project.
- 4Or upload it in the Claude apps. In the Claude apps, go to Settings, then Capabilities, then Skills, and upload the skill.
- 5Invoke it explicitly. Type /chinese-code-review in your request and describe the review task. It will not trigger on its own.
What does the chinese-code-review skill make the agent do?
When you explicitly invoke it, the agent follows a Chinese-language code review style guide. It helps you phrase feedback as suggestions or questions rather than commands, tags each comment with a priority level, and structures summaries and checklists.
The skill also covers mixed Chinese-English comments and bilingual commit message conventions. It is a reference document, not a tool: it does not read your repository and does not run anything. It shapes wording and structure, so it cannot find bugs for you.
- Feedback phrased as suggestions or questions, for example 这里是否考虑过 Z 的情况？ instead of 这里写错了
- Priority labels: [必须修复] (must fix), [建议修改] (suggested change), [仅供参考] (reference only), [问题] (question for the author)
- Review comment templates, review summaries that open with praise, and a pre-submit checklist
- Guidance on when to write comments in Chinese versus English, and Conventional Commits in Chinese
How do you install the chinese-code-review skill?
Download the ZIP file from the skill page on this site. Unzip it so that the skill folder, which contains SKILL.md, ends up in one of the following locations.
For a personal setup available across your projects, put it in ~/.claude/skills/. For a single project, put it in that project's .claude/skills/ folder. You can also upload the skill in the Claude apps under Settings → Capabilities → Skills.
- Personal: ~/.claude/skills/
- Project only: .claude/skills/ inside your project folder
- Claude apps: Settings → Capabilities → Skills, then upload the skill
How do you trigger the skill?
Do not expect the skill to switch on from a normal request. It is set to run only when you explicitly invoke it with /chinese-code-review, and it is not triggered automatically based on context. Include the command in your message when you want the Chinese review style applied.
The skill does not define a specific argument format, so after the command simply describe the review task in plain language, such as the code you want commented on and the tone you want.
- Works: include /chinese-code-review in your request, then describe the review task
- Does not work as intended: asking for a review without the command, expecting the skill to activate on its own
/chinese-code-reviewWhat does the output look like?
A typical comment leads with a priority tag, names the problem and its location, explains the reason, and gives a concrete suggestion. The source template below shows this structure with a SQL injection example.
For comments where you are unsure of the author's intent, the skill recommends asking a question first. For praise-worthy code, it recommends saying what you checked, rather than writing a bare LGTM.
- Use [必须修复] only for security holes, data loss risks, and logic errors that block merging
- Use [建议修改] for performance, maintainability, and missing validation
- Use [仅供参考] for naming and style suggestions the author may ignore
- Use [问题] when you need the author to explain their intent
[必须修复] SQL 注入风险
第 42 行：用户输入直接拼接到 SQL 语句中。
原因：攻击者可以通过 name 参数注入恶意 SQL。
建议：使用参数化查询。What does the skill need, and what are the safety notes?
The skill lists no requirements. It does not run scripts and does not use the network. Because it is a set of written guidelines, installing it only adds a folder of Markdown instructions to your agent setup.
Since it does not read your code, anything it says about a file comes from what you paste or describe in the conversation. Keep reviewing the code yourself, and treat its output as wording guidance.
- Requirements: none listed
- Runs scripts: no
- Uses network: no
- Files included: SKILL.md
- Licence: MIT
What tips help you get the most from it?
Pair the skill with automated tools for style. The guide itself says formatting issues should go to ESLint, Prettier, gofmt and similar tools, so reviewers can focus on logic, security and performance.
Use the review order the skill suggests: architecture, correctness, security, performance, maintainability, then style. Read the PR description and linked issue before you start.
- Keep severity honest: a gentle tone is fine, but [必须修复] must mean must fix
- Give a summary after each review: one-line verdict, praise first, then problems grouped by priority
- Write commit messages in the format the skill shows, for example fix(支付): 修复 ... with an optional body and Closes #number
- For open-source or international projects, the skill suggests English commit messages and comments
What people use it for
- Rewriting a harsh review comment into a suggestion-style comment that still names the bug
- Sorting a batch of review notes into [必须修复], [建议修改], [仅供参考] and [问题] before posting
- Drafting a review summary for a pull request, with praise first and problems listed by priority
- Writing Chinese commit messages in Conventional Commits format for an internal team project
Frequently asked questions
Is the chinese-code-review skill free?
The skill is licensed under the MIT licence, as stated on its page. The source does not list prices, so check the skill page for any other terms before you rely on it.
What are the requirements for chinese-code-review?
The skill lists no requirements. It does not run scripts and does not use the network, and it ships as a single SKILL.md file.
Does the skill review my code for bugs?
No. The skill only shapes the wording, priority labels and structure of review comments. It does not read your repository or detect bugs, so pair it with your own review and automated tools.
Why isn't the skill triggering when I ask for a code review?
The skill is designed to run only when you explicitly type /chinese-code-review. It does not activate automatically from context, so include the command in your request.
Can I use it for an English-only project?
The skill is written for Chinese teams and mixed-language use. The source says projects that require English-only communication are not a good fit, and that international projects should use English commit messages.
What are alternatives to chinese-code-review?
The source does not compare this skill with other tools. For automatic style checks, the guide points to ESLint, Prettier and gofmt, which handle formatting but not review wording. For bug detection, you need a tool that actually inspects code, since this skill does not.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you write code review comments in Chinese and want consistent priority labels, tactful wording and standard commit messages. Skip it if you need automated bug detection, want the agent to read your repository, or work in an English-only team.
Download the skill