code-review

Review Flutter and Dart code changes for correctness and quality.

2|Updated Aug 13, 2023
One-click install
npx skills add https://github.com/NNPopov/movie-theater-tickets --skill code-review-nnpopov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/NNPopov/movie-theater-tickets/tree/main/src/clients/.claude/skills/code-review
Command: npx skills add https://github.com/NNPopov/movie-theater-tickets --skill code-review-nnpopov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns ad hoc pull request review into a repeatable, objective process for Flutter and Dart projects, helping reviewers catch bugs, regressions, and missing tests before merge.

Core Features & Use Cases

  • Structured review checklist: Checks location, naming, responsibility, readability, correctness, maintainability, error handling, security, performance, documentation, and style.
  • Flutter-specific validation: Calls out rebuild scope, key usage, disposal of controllers and streams, and const opportunities.
  • Change-set evaluation: Assesses whether the diff is focused, whether tests cover new logic, and whether CI or analyzer issues need to be flagged.
  • Use case: Review a feature branch that updates a Flutter screen and confirm the implementation is safe, efficient, and testable before approving.

Quick Start

Ask for a structured code review of the attached Flutter or Dart diff and include the target branch, changed files, and any known concerns.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review Flutter pull requests for common Dart code quality issues?

Reviewing Flutter pull requests involves checking Dart code changes against a structured checklist for correctness, security, performance, and style. The process verifies logic, error handling, and documentation to catch bugs before merge.

What Flutter-specific performance problems should I look for in a Dart code review?

When reviewing Flutter code, look for widget rebuild scope, improper key usage, undisposed controllers and streams, and missed const constructor opportunities. These specific checks ensure efficient mobile app rendering and resource management.

Can I use a structured checklist to audit a Flutter feature branch diff?

Yes, you can audit a Flutter feature branch diff using a structured checklist that evaluates responsibility, readability, maintainability, and test coverage. This confirms whether the implementation is safe and testable before approving the merge.

How do I verify test coverage for new logic in a Dart merge request?

Verify test coverage in a Dart merge request by evaluating whether the change-set diff includes tests for newly added logic. The review process flags missing tests and CI or analyzer issues that need attention before merging.

Does this code review process work for general branch audits in mobile app repositories?

Yes, the code review process applies to branch audits and diff inspections in mobile app repositories using Flutter and Dart. It validates generated files, logic, and security across various change-set evaluations.