- name
SKILL.md
Die Skill-Datei bleibt im Repository des Herausgebers.
Fügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add evanca/flutter-ai-rules --skill code-review -a cursor -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add evanca/flutter-ai-rules --skill code-review -a claude-code -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add evanca/flutter-ai-rules --skill code-review -a codex -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add evanca/flutter-ai-rules --skill code-review -a grok -ySenden Sie die kopierte Nachricht in einem Grok Bot-Chat. Der Bot ruft diese SKILL.md von GitHub ab und fügt sie den Skills hinzu, die alle Ihre Bots gemeinsam nutzen.
Install this skill: https://github.com/evanca/flutter-ai-rules/tree/HEAD/skills/code-reviewVom Herausgeber
Perform structured, objective code reviews for Flutter/Dart projects following a repeatable checklist.
Use this skill when:
main, master, develop).Checkpoint: If the branch is behind the target, flag it before proceeding.
Iterate through each changed file. For every file, verify the following:
For generated files (e.g., *.g.dart, *.freezed.dart): confirm they are up-to-date and not manually modified.
Scope discipline: Your job is not to comment on every change — it's to find errors and concrete improvement areas and comment on those. Don't manufacture comments where the code is fine.
(Note: The following is just an example using Bloc/Cubit; apply similar principles to Riverpod, Provider, or your chosen state management package.)
// BAD — rebuilds entire tree on every state change
BlocBuilder<MyCubit, MyState>(
builder: (context, state) => EntireScreen(state: state),
);
// GOOD — scope rebuilds to the widget that actually changes
BlocSelector<MyCubit, MyState, String>(
selector: (state) => state.title,
builder: (context, title) => Text(title),
);
Key usage on dynamically generated widgets.dispose() is called for controllers, streams, and animation controllers.const constructors are used where possible.For each file, check for common code smells. Use refactoring.guru/refactoring/smells for definitions and suggested refactorings.
Verify test coverage explicitly — this is easy to skip and easy to fake, so be deliberate:
Checkpoint: If CI is red or tests are missing for new logic, flag as a blocking issue.
After the per-file pass, decide the outcome:
suggestion, minor, or major.By default, provide the review as a chat response — a structured response covering each file:
suggestion / minor / major) and a concrete fix suggestion.Approved, Approved with suggestions, or Changes requested.Posting comments online (opt-in only). After presenting the chat review, ask the user whether they'd prefer you to also post these comments online on the PR/MR — so the team can see them, review them, and reply. Only post online if the user explicitly says yes. Never post to the platform on your own initiative.
When the user does opt in, post issues as inline comments anchored to the right file and line (use proper position fields), with the conclusion/key-concerns as a top-level review comment and an approval when warranted. This requires a review-bot access token for the platform (GitHub/GitLab); if one isn't configured, let the user know and ask them to set it up before posting.
Token safety. The token is a secret. You may check whether it exists and report its length to confirm it's configured, but never read, echo, log, print, or otherwise reveal the token value — not in chat, not in a file, not in a commit. Pass it to
curlonly by referencing the env var (e.g.$GITLAB_TOKEN), never by inlining the literal value, and avoidcurl -v/--verbose(it prints the auth header). This is enforced by aPreToolUsehook (scripts/protect-token.sh) that blocks any Bash command which would expose the value. See the "Handling the token safely" section in each reference file for the safe existence/length check.The hook fires in both the Claude Code CLI and the Agent SDK. (SDK apps that set
settingSources/setting_sourcesexplicitly must include"project"for skill hooks to load; it's included by default.)For platform-specific API details, curl formats, and approval steps, follow:
- GitLab → references/gitlab-posting.md (uses the
GITLAB_TOKENenv var)- GitHub → references/github-posting.md (uses the
GITHUB_TOKENenv var)
Use when asked to review a PR, MR, branch, or diff, audit changed files, or check code quality.
---name: code-reviewdescription: Use when asked to review a PR, MR, branch, or diff, audit changed files, or check code quality.---# skills/code-review/SKILL.mdFAQ
Laden Sie skills/code-review/SKILL.md vom Herausgeber herunter oder kopieren Sie den Pfad und öffnen Sie das Repository. PlugMCP listet den Skill und hostet die Datei nicht.
Der Herausgeber pflegt es unter https://github.com/evanca/flutter-ai-rules.
Claude, Cursor, Codex und Grok Build können eine SKILL.md lesen, die Sie aus dem Repository des Herausgebers hinzufügen. Grok Bot installiert sie, wenn Sie den Link zum GitHub-Ordner des Skills in einem Chat senden.