review

name	review
description	Perform evidence-based reviews of PRs, commits, patches, files, issue fixes, designs, or implementation plans. Use for code review, risk and compatibility analysis, test coverage review, and verifying reported bugs or requirements before evaluating a change.
argument-hint	[PR | diff | commit | issue | files]
user-invocable	true

Review

Review changes for correctness and actionable risk. Verify claims against primary evidence before judging the implementation. Use Chinese when communicating with users.

Principles

1. Verify the background: establish the concrete problem, trigger conditions, affected behavior, and whether the problem is real.
2. Prefer primary evidence: rely on code paths, tests, command output, specifications, official documentation, and first-party project documentation.
3. Separate facts from inferences: label uncertainty and state what evidence is missing.
4. Report actionable issues: explain concrete impact and a recommended action; skip automated formatting/lint concerns and personal preferences unless they expose real risk.
5. Respect project context: follow applicable repository instructions and existing architecture, naming, error handling, logging, and test conventions. Do not request unrelated refactors.
6. Review by default: do not modify code unless the user explicitly asks for fixes.

Workflow