Menü
Use when completing tasks, implementing major features, or before merging to verify Flutter code meets requirements
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Creates a new Flutter project with Clean Architecture, domain pattern boilerplate, and production-ready setup
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation using Clean Architecture principles.
Use when you have a written implementation plan to execute with review checkpoints
Use when facing 2+ independent Flutter tasks that can be worked on without shared state or sequential dependencies
Use when you have a design or requirements for a multi-step Flutter feature, before touching code
Use when executing Flutter implementation plans with independent tasks in the current session
| name | flutter-review-request |
| description | Use when completing tasks, implementing major features, or before merging to verify Flutter code meets requirements |
Dispatch flutter-craft:flutter-code-reviewer subagent to catch issues before they cascade.
Core principle: Review early, review often.
Announce at start: "I'm using the flutter-review-request skill to request code review."
Mandatory:
Optional but valuable:
BASE_SHA=$(git rev-parse HEAD~1) # or origin/main
HEAD_SHA=$(git rev-parse HEAD)
Use Task tool with flutter-craft:flutter-code-reviewer type:
Task tool:
subagent_type: "flutter-craft:flutter-code-reviewer"
prompt: |
## What Was Implemented
{WHAT_WAS_IMPLEMENTED}
## Requirements/Plan
{PLAN_OR_REQUIREMENTS}
## Git Range to Review
Base: {BASE_SHA}
Head: {HEAD_SHA}
## Files Changed
{FILES_CHANGED}
Please review for:
- Clean Architecture compliance
- State management patterns
- Flutter best practices
- Test coverage (priority-based)
| Issue Severity | Action |
|---|---|
| Critical | Fix immediately before proceeding |
| Important | Fix before proceeding to next task |
| Minor | Note for later, can proceed |
The full checklist (Clean Architecture, state management, widget composition,
Dart style, priority-based test coverage including golden tests) lives in the
reviewer itself: agents/flutter-code-reviewer.md. It is the single source of
truth — do not duplicate it here; the dispatched agent applies it.
[Just completed Task 3: Add AuthBloc]
You: Let me request code review before proceeding.
BASE_SHA=$(git rev-parse HEAD~3)
HEAD_SHA=$(git rev-parse HEAD)
[Dispatch flutter-craft:flutter-code-reviewer subagent]
WHAT_WAS_IMPLEMENTED: Authentication feature with login/logout
PLAN_OR_REQUIREMENTS: Task 1-3 from docs/plans/auth-plan.md
BASE_SHA: a7981ec
HEAD_SHA: 3df7661
FILES_CHANGED:
- lib/features/auth/domain/entities/user.dart
- lib/features/auth/domain/repositories/auth_repository.dart
- lib/features/auth/data/repositories/auth_repository_impl.dart
- lib/features/auth/presentation/bloc/auth_bloc.dart
[Subagent returns]:
### Strengths
- Clean layer separation
- Proper BLoC state handling
- Good error states
### Issues
#### Important
- Missing AuthBloc unit tests (auth_bloc_test.dart)
- No error boundary in LoginScreen
#### Minor
- Consider using freezed for state classes
### Assessment
**Ready to merge: With fixes**
Fix the Important issues before proceeding.
You: [Add AuthBloc tests, add error boundary]
[Continue to Task 4]
Never:
If reviewer wrong:
After receiving review feedback, you MUST invoke: → flutter-craft:flutter-review-receive
Process the feedback systematically before continuing.