Claude-skill-registry flutter-code-review
Review Flutter app PRs for bugs, UX issues, performance regressions, missing tests, and readability; include app code, packages/plugins, and CI config. Use when asked to review a Flutter PR, do a Flutter code review, or find bugs in Flutter repositories.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/flutter-code-review" ~/.claude/skills/majiayu000-claude-skill-registry-flutter-code-review && rm -rf "$T"
manifest:
skills/data/flutter-code-review/SKILL.mdsource content
Flutter Code Review
Overview
Provide structured PR reviews for Flutter apps with prioritized findings. Focus on bugs first, then UX, performance, tests, and readability, and report issues as bullet points with file/line references.
Workflow
- Identify scope: review the diff and list touched files (Flutter app code, package/plugin code, CI files).
- Bugs/regressions: check state management, async flows, widget lifecycle, null safety, error handling, navigation, permissions, and data persistence.
- UX issues: verify loading/empty/error states, accessibility, layout on small screens, and gesture conflicts.
- Performance: watch for rebuild hotspots, unnecessary
, large lists without virtualization, expensive work on UI thread, and image caching.setState - Tests: ensure new logic is covered; suggest or run
andflutter test
as appropriate.flutter analyze - Report findings ordered by severity with short rationales and precise file/line references.
Output Format
Use bullets only:
- Findings first, ordered by severity, each with
and a brief rationale.path:line - Then questions/assumptions if clarification is needed.
- Then a short change summary if helpful.
Example bullet:
Potential NPE whenlib/screens/home_screen.dart:120
is null; guard before accessing fields.currentSong