chinese-code-review

Use suggestion-based phrasing instead of commands, and label each comment with a priority tag like [必须修复] or [建议修改]. The Skill provides templates for common issues such as SQL injection and concurrency bugs, including cause, fix, and reference links.

Use four levels: [必须修复] for security and logic errors blocking merge, [建议修改] for performance and maintainability issues, [仅供参考] for optional style suggestions, and [问题] when you need the author to explain intent.

Use Chinese for business logic explanations, complex algorithm notes, and internal TODOs; use English for identifiers, error messages, logs, and open-source projects. Keep a space between Chinese and English text and retain technical terms like debounce in English.

Frame feedback as questions about their design choices rather than assertions, such as asking why recursion was chosen over iteration and noting stack overflow risk. Code review should address the code, not the person, regardless of seniority.

It should only run when the user explicitly invokes /chinese-code-review. It is not meant to auto-trigger from context, and it focuses on communication style rather than automated linting, which tools like ESLint or gofmt already handle.