[FEATURE] Allow selecting a model for the built-in /code-review skill

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Currently, the built-in /code-review skill appears to inherit the model from the current session by default. When the current session is using a very capable but usage-limited or expensive model, running /code-review can quickly consume the available usage quota.

This is a common issue during software development because code review may be invoked frequently, and users may not always need the same high-tier model for every review. As a result, using /code-review from a high-tier model session can make the workflow less practical and discourage frequent use of the feature.

Proposed Solution

Add an optional argument to /code-review that allows users to specify which model should be used for the review.

For example:

/code-review --model <model-name>

Ideally, users could choose from available models such as higher-quality models for complex reviews and faster or lower-cost models for routine reviews. If no model is specified, /code-review could continue using the current default behavior.

This would give users more control over usage, cost, and review quality while improving the development experience.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

Other

Use Case Example

_No response_

Additional Context

_No response_