agentsclimarketplace

Flutter code review

Skill Desquared/agents-rules-skills/skills/flutter-code-review

Use when reviewing Flutter code for correctness, architecture compliance, design system usage, linting, or testing coverage. Also use before merging a PR or when the user asks for a code review of Dart or Flutter files.From its SKILL.md

Install
npx -y skills add Desquared/agents-rules-skills --skill flutter-code-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, as published. Nobody here has run it

Code Review Skill

7 Criteria

1. Functionality (πŸ”΄ Blocker)

  • Logic errors, missing error handling, null safety violations

2. Readability (🟠 Major)

  • Clear naming, proper comments, no dead code

3. Optimization (🟠 Major)

  • Unnecessary rebuilds, N+1 queries, missing const

4. Architecture (🟠 Major)

  • data/domain/view pattern, repository pattern, @injectable DI

5. Design System (🟠 Major)

  • ColorPalette, Spacing, Project Design System Widgets (no hardcoded)

6. Linting (πŸ”΄ Blocker)

  • flutter analyze must pass (zero errors)

7. Testing (Optional)

  • 90%+ unit, 50%+ widget coverage (suggest, don't block)

Quick Checks

// ❌ Hardcoded color
Text('Hi', style: TextStyle(color: Colors.red))

// βœ… Use ColorPalette
Text('Hi', style: TextStyle(
  color: ColorPalette.coloursBasicText.platformBrightnessColor(context),
))

// ❌ Business logic in widget
final total = items.fold(0, (s, i) => s + i.price);

// βœ… Logic in Bloc/Cubit
@injectable class MyBloc { ... }

// ❌ No error handling
Future<Data> fetch() async {
  return await api.call();
}

// βœ… Try-catch
Future<Data> fetch() async {
  try {
    return await api.call();
  } catch (e) {
    throw NetworkException(e.toString());
  }
}

Severity

  • πŸ”΄ Blocker: Must fix (functionality, security, linting)
  • 🟠 Major: Should fix (performance, architecture, design system)
  • 🟒 Minor: Nice to fix (naming, comments)

Process

  1. flutter analyze (must pass)
  2. Check file structure (data/domain/view)
  3. Verify design system usage
  4. Check state management (@injectable)
  5. Verify error handling
  6. Check tests (suggest improvements)

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.