review-code

Review code at $ARGUMENTS across 6 dimensions: Correctness, Security, Performance, Readability, Testing, and Architecture.

Output Mode

1. Detect the user's preferred language from the request, surrounding discussion, and repository context.
2. If the user writes in Chinese, or the request is mixed Chinese plus English technical terms, write the human-facing review in Chinese.
3. If the user writes in English, write the review in English.
4. Keep identifiers, API names, CLI commands, filenames, and code snippets in their original language. Do not force-translate technical terms.
5. Treat bundled templates as structure references, not literal language locks. Localize headings, labels, and summaries to the chosen output mode.

Review Tone

Chinese mode

• Prefer suggestion-style wording over command-style wording.
• Prefer questions when intent is uncertain, but do not hide blocking issues behind vague language.
• State severity clearly. A blocking issue should still read like a blocking issue.
• Praise concrete good practices when they matter, but do not let praise dilute must-fix findings.
• Avoid turning review into a style argument when tools or project standards can settle it automatically.