Agent not registered in AGENTS.md

The root AGENTS.md file is the single source of truth for agent discovery and orchestration — it's what Claude uses to decide when to delegate to a specialized agent. Every other language reviewer (kotlin-reviewer, go-reviewer, python-reviewer, java-reviewer, rust-reviewer, typescript-reviewer, etc.) is listed there with a clear purpose and "When to Use" column. flutter-reviewer is missing entirely.

Additionally, the preamble in AGENTS.md currently reads:

"providing 27 specialized agents, 114 skills, 59 commands…"

This count needs to be updated to 28 after this PR merges.

Without adding the entry to AGENTS.md, the orchestration system has no signal to invoke this agent for Flutter projects, making it effectively invisible to the pipeline.

Suggested addition to the Available Agents table in AGENTS.md:

| flutter-reviewer | Flutter/Dart code review | Flutter/Dart projects |

Skill format diverges from project convention

CLAUDE.md documents the expected skill format as:

"Skills: Clear sections (When to Use, How It Works, Examples)"

All skills are expected to open with those three standard sections so consumers know at a glance when the skill applies and how to invoke it. This file opens directly with a flat checklist under ## 1. General Project Health — there is no ## When to Use, ## How It Works, or ## Examples section.

While the checklist content is thorough, omitting the standard preamble sections means this skill doesn't follow the same discoverability contract as the rest of the skill library. Consider adding the three standard sections (even if brief) before the numbered checklist to keep the format consistent.

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

Step numbering skips "Step 2a"

The workflow goes Step 2 → Step 2b with no Step 2a in between. While functionally harmless (the intent is clear), the label 2b strongly implies a 2a exists somewhere. Readers may scan upward looking for it.

The kotlin-reviewer.md has the same pattern, so this is an inherited inconsistency in the project. Consider either renaming Step 2b to Step 3 and re-numbering subsequent steps, or labelling the preceding step Step 2a explicitly — whichever aligns with the pattern you'd prefer to standardise across all language reviewers.

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

P1: The Dart Idioms section incorrectly lists requireNotNull as a preferred null-safety alternative. This is a Kotlin function that does not exist in Dart's standard library. The agent will recommend invalid code to Flutter/Dart developers.

Check if this issue is valid — if so, understand the root cause and fix it. At agents/flutter-reviewer.md, line 122:

<comment>The Dart Idioms section incorrectly lists `requireNotNull` as a preferred null-safety alternative. This is a Kotlin function that does not exist in Dart's standard library. The agent will recommend invalid code to Flutter/Dart developers.</comment>

<file context>
@@ -0,0 +1,243 @@
+### Dart Idioms (MEDIUM)
+
+- **Missing type annotations / implicit `dynamic`** — Enable `strict-casts`, `strict-inference`, `strict-raw-types` to catch these
+- **`!` bang overuse** — Prefer `?.`, `??`, `case var v?`, or `requireNotNull`
+- **Broad exception catching** — `catch (e)` without `on` clause; specify exception types
+- **Catching `Error` subtypes** — `Error` indicates bugs, not recoverable conditions
</file context>

P2: Provider disposal documentation is oversimplified - disposal is only automatic with create constructor, not with .value which requires manual disposal

Check if this issue is valid — if so, understand the root cause and fix it. At skills/flutter-dart-code-review/SKILL.md, line 419:

<comment>Provider disposal documentation is oversimplified - disposal is only automatic with `create` constructor, not with `.value` which requires manual disposal</comment>

<file context>
@@ -0,0 +1,435 @@
+| UI consumer | `BlocBuilder` | `ConsumerWidget` | `Consumer` | `Obx`/`GetBuilder` | `Observer` | `Watch` | `setState` |
+| Selector | `BlocSelector`/`buildWhen` | `ref.watch(p.select(...))` | `Selector` | N/A | computed | `computed()` | N/A |
+| Side effects | `BlocListener` | `ref.listen` | `Consumer` callback | `ever()`/`once()` | `reaction` | `effect()` | callbacks |
+| Disposal | auto via `BlocProvider` | `.autoDispose` | auto via `Provider` | `onClose()` | `ReactionDisposer` | manual | `dispose()` |
+| Testing | `blocTest()` | `ProviderContainer` | `ChangeNotifier` directly | `Get.put` in test | store directly | signal directly | widget test |
+
</file context>