chinese-code-review

Use suggestion-style phrasing instead of commands, such as "建议考虑用 X，因为 Y" rather than "你必须改成 X". Pair the softer tone with explicit priority labels like [必须修复] so critical issues are never lost in politeness.

Use four standard labels: [必须修复] 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, TODOs, and internal documentation. Use English for variable and function names, error messages, logs, public API docs, and comments in open-source projects targeting international audiences.

Follow the format <类型>(<范围>): <简要描述> using standard types like feat, fix, refactor, and perf, for example "fix(支付): 修复微信支付回调重复处理的问题". Add an optional body explaining cause and solution, plus issue references like Closes #1234.

Frame feedback as questions rather than judgments, such as asking why recursion was chosen over iteration and whether deep recursion risks stack overflow. This keeps review focused on the code rather than hierarchy while still surfacing real risks.

A bare LGTM provides no evidence the code was actually examined, leaving no accountability when bugs slip through. Even for good code, list the aspects you verified, such as concurrency safety, error handling, and backward compatibility.