code-review
Use when asked to review a PR, MR, branch, or diff, audit changed files, or check code quality.
npx skills add evanca/flutter-ai-rules --skill code-review --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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** —
- When to Use
- Review Workflow
- Step 1 — Validate branch and merge target
- Step 2 — Discover changes
- Step 3 — Review each file
- Step 4 — Evaluate the overall change set
- Step 5 — Verify CI and tests
- Wrap-Up
- Feedback Standards
- Output Format
What does the code-review skill do?
Use when asked to review a PR, MR, branch, or diff, audit changed files, or check code quality.
How do I install it?
Run `npx skills add evanca/flutter-ai-rules --skill code-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From evanca/flutter-ai-rules, a repository with 604 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.