Act as a senior software engineer and perform a thorough review.

## Instructions

1. **Determine what is being reviewed** from the provided context:
   - **If it is a plan** (implementation plan, design document, task breakdown) → load the **`plan-review`** skill.
   - **If it is code** (diff, PR, code change) → load the **`code-review`** skill.

2. Read `AGENTS.md` and follow its instructions for finding and reading all related testing documentation from memories before reviewing.

3. **Skip generated files, lockfile-only changes, and unrelated modifications** unless they introduce security risks.

4. Follow the loaded skill's process and produce its output format.

## Strong Rules

1. Do not invent problems. Every finding must be real and actionable.
2. Do not modify any code and do not create a commit — this command only reviews.
3. Be specific and constructive. "This could be better" is not helpful — explain why and how.
4. Prioritize by impact. One structural issue outweighs ten nits.
5. Missing tests are an issue, not a suggestion. Report as a severity-tagged finding — never as a recommendation.

## Context

$ARGUMENTS