Use when completing tasks, implementing major features, or before merging to verify Flutter code meets requirements
/plugin marketplace add vp-k/flutter-craft/plugin install vp-k-flutter-craft-plugins-flutter-craft@vp-k/flutter-craftThis skill inherits all available tools. When active, it can use any tool Claude has access to.
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 reviewer will check:
flutter analyze clean)[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.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.