code-review

Review Flutter and Dart pull requests for correctness, security, style, testing, and documentation.

611|60|Updated Apr 22, 2025
One-click install
npx skills add https://github.com/evanca/flutter-ai-rules --skill code-review-evanca
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/evanca/flutter-ai-rules/tree/main/skills/code-review
Command: npx skills add https://github.com/evanca/flutter-ai-rules --skill code-review-evanca

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, objective framework to review Flutter and Dart pull requests, ensuring consistency and high-quality changes.

Core Features & Use Cases

  • Branch and Merge Target validation: ensures the target branch is correct and up-to-date before review.
  • Change discovery and per-file analysis: inventories changed files and evaluates each for correctness, naming, readability, and maintainability.
  • Overall change set and CI alignment: checks scope, description accuracy, and testing coverage; recommends CI checks.

Quick Start

Provide the pull request or branch details and the list of changed files to initiate a structured code review.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a Flutter pull request for correctness and style?

To review a Flutter pull request, provide the branch details and changed files to initiate a structured code review that evaluates correctness, naming, readability, and maintainability per file.

What should a Dart code review checklist cover?

A Dart code review checklist should cover correctness, security, style, testing, and documentation, while also validating that the merge target branch is correct and up-to-date.

Can I use an automated review checklist for Dart merge requests?

Yes, you can apply an automated review checklist to Dart merge requests by inventorying changed files and evaluating the overall change set against CI alignment and testing coverage requirements.

How do I validate a merge target branch before reviewing Flutter changes?

Validating a merge target branch before reviewing Flutter changes ensures the target is correct and up-to-date, preventing integration conflicts before analyzing the change set scope and description accuracy.

Does the review process check CI alignment for Flutter pull requests?

Yes, the review process checks CI alignment for Flutter pull requests by evaluating testing coverage and recommending specific CI checks based on the overall change set analysis.