Code Review
Follow the review scope and comparison base stated by the user. Do not replace a file, function,
commit, branch, pull request, merge request, or other explicit target with the current uncommitted
diff. For current local uncommitted working-tree changes, inspect staged, unstaged, and untracked
changes relative to HEAD. When the scope or base is genuinely ambiguous, inspect the available
context and ask only if proceeding would materially change the review.
Inspect the complete requested change before concluding. Read the applicable repository instruction
files and verify each potential issue against the current code, surrounding call sites, tests, and
relevant data flow.
Review calibration
- Report only discrete, actionable defects that affect correctness, security, performance, or
maintainability enough that the author would likely fix them.
- Report issues introduced by the requested change when the task supplies a comparison base. Do not
report pre-existing defects as change regressions.
- State the concrete input, state, environment, or execution path that triggers the problem and the
resulting impact.
- Do not rely on unstated assumptions about intent. Verify affected callers or consumers before
claiming cross-component impact.
- Ignore formatting, spelling, routine lint, subjective preferences, broad refactors, and missing
tests unless they demonstrate a concrete regression.
- Remove speculative, duplicated, already-handled, or unsupported findings before responding.
- Continue after the first issue and return every qualifying finding.
- Keep any referenced line range as small as practical.
Review-only behavior
Treat a review request as read-only unless the user also asks for fixes. Use inspection and
read-only Git commands as needed, but do not edit files, create commits, push branches, or open
merge requests.
Response
Return the review in normal Markdown unless the host supplies a structured review response protocol;
when it does, follow that protocol instead. Keep the investigation and verification process out of
the finding text. For each finding, write a compact comment containing only the concrete trigger and
resulting impact, plus one minimal remediation direction when it materially helps. Include the
relevant file and shortest useful line range. If no actionable issues remain, say so directly and
briefly.
1---2name: code-review3description:4 Review local uncommitted changes, commits, branches, pull requests, files, functions, or other5 user-specified code scopes for concrete defects. Follow the scope and comparison base named by the6 user. Do not use for ordinary code explanation, debugging, implementation, or fix requests that do7 not ask for a review.8metadata:9 source: https://skillmd.com/skills/minimax-ai/code-review10---1112# Code Review1314Follow the review scope and comparison base stated by the user. Do not replace a file, function,15commit, branch, pull request, merge request, or other explicit target with the current uncommitted16diff. For current local uncommitted working-tree changes, inspect staged, unstaged, and untracked17changes relative to HEAD. When the scope or base is genuinely ambiguous, inspect the available18context and ask only if proceeding would materially change the review.1920Inspect the complete requested change before concluding. Read the applicable repository instruction21files and verify each potential issue against the current code, surrounding call sites, tests, and22relevant data flow.2324## Review calibration2526- Report only discrete, actionable defects that affect correctness, security, performance, or27 maintainability enough that the author would likely fix them.28- Report issues introduced by the requested change when the task supplies a comparison base. Do not29 report pre-existing defects as change regressions.30- State the concrete input, state, environment, or execution path that triggers the problem and the31 resulting impact.32- Do not rely on unstated assumptions about intent. Verify affected callers or consumers before33 claiming cross-component impact.34- Ignore formatting, spelling, routine lint, subjective preferences, broad refactors, and missing35 tests unless they demonstrate a concrete regression.36- Remove speculative, duplicated, already-handled, or unsupported findings before responding.37- Continue after the first issue and return every qualifying finding.38- Keep any referenced line range as small as practical.3940## Review-only behavior4142Treat a review request as read-only unless the user also asks for fixes. Use inspection and43read-only Git commands as needed, but do not edit files, create commits, push branches, or open44merge requests.4546## Response4748Return the review in normal Markdown unless the host supplies a structured review response protocol;49when it does, follow that protocol instead. Keep the investigation and verification process out of50the finding text. For each finding, write a compact comment containing only the concrete trigger and51resulting impact, plus one minimal remediation direction when it materially helps. Include the52relevant file and shortest useful line range. If no actionable issues remain, say so directly and53briefly.