code-review

# Code Review Skill Perform structured, objective code reviews for Flutter/Dart projects following a repeatable checklist. ## When to Use Use this skill when: * Asked to review a pull request, merge request, or branch. * Evaluating changed, added, or deleted files for correctness and quality. * Auditing a diff before merging. * Checking whether new code meets project standards. --- ## Review Workflow ### Step 1 — Validate branch and merge target 1. Confirm the current branch is a **feature, bugfix, or PR/MR branch** — not the project's primary branch (e.g. `main`, `master`, `develop`). 2. Verify the branch is **up-to-date** with the target branch (no unresolved conflicts). 3. Identify the **target branch** for the merge. **Checkpoint:** If the branch is behind the target, flag it before proceeding. ### Step 2 — Discover changes 1. List all **changed, added, and deleted files**. 2. For each change, look up the **commit title** and review how connected components are implemented. 3. **Analyze the change**: is it clear *why* the change was made? If not, dig into the connected methods and files until it is. When you report, name **which connected files/methods you analyzed and why** — this shows the change was understood, not assumed. 4. **Never assume** a change is correct without investigating the implementation. 5. If a change remains unclear after investigation, **note this explicitly** in the report. ### Step 3 — Review each file Iterate through each changed fil...