Code Review
Use when asked to review a PR, MR, branch, or diff, audit changed files, or check code...
Install
npx skills add evanca/flutter-ai-rules --skill code-review -g -a claude-code -y- Repository
- evanca/flutter-ai-rules668
- Category
- Git and review
- Updated
- 5d ago
- License
- MIT
- Context cost
- Mediumabout 2,321 tokens
- Runs scripts
- Yes, review before use
What it does
Use when asked to review a PR, MR, branch, or diff, audit changed files, or check code quality.
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
- Confirm the current branch is a feature, bugfix, or PR/MR branch, not the project's primary branch (e.g.
main,master,develop). - Verify the branch is up-to-date with the target branch (no unresolved conflicts).
- Identify the target branch for the merge.
Checkpoint: If the branch is behind the target, flag it before proceeding.
Step 2, Discover changes
- List all changed, added, and deleted files.
- For each change, look up the commit title and review how connected components are implemented.
- 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.
- Never assume a change is correct without investigating the implementation.
- If a change remains unclear after investigation, note this explicitly in the report.
Step 3, Review each file
Iterate through each changed file. For every file, verify the following:
