Menu
Post-generation workflow that orchestrates code generation and quality verification for created or modified Dart files.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Execute code generation for created source files. Handles build_runner (freezed, json_serializable, retrofit, auto_route, theme_tailor, flutter_gen) and localization via Melos. Use after creating or modifying source files that require code generation.
Automate the full submodule-change lifecycle: detect modified submodules, create a feature branch inside the submodule, commit, push, generate the GitLab MR URL, then bump the submodule pointer in the parent repo as a separate commit. Picks up any intermediate state (dirty / staged / committed but unpushed / pushed but parent pointer not bumped) and continues from there. Use when you've edited a file inside `docs/flutter-rules/` (or any other submodule) and need to land the change properly.
Create Retrofit API interfaces and DTOs with proper nullability, JSON serialization, and code generation. Use when adding new API clients or data transfer objects.
Create Alchemist golden tests for screens, widgets, and UIKit components. Use when adding visual regression tests for a View, ViewModel-driven screen, reusable widget, or UIKit element.
Build a GitLab merge request for the current branch — generates title and description following the project's MR template, parses JIRA ticket from branch name, summarizes the diff, runs pre-push safety checks, pushes the branch, and outputs a ready-to-open GitLab "new MR" URL. Use when finishing a feature branch.
Create local data storage (key-value/secure storage) or database DAO (Drift/SQLite) implementations with interfaces, DTOs, and DI wiring. Use when adding persistent local storage or database DAOs for a feature.
Based on SOC occupation classification
| name | after-generation |
| description | Post-generation workflow that orchestrates code generation and quality verification for created or modified Dart files. |
Orchestration skill to run after creating or modifying *.dart files. Executes two phases in order.
Trigger: You created or modified files that use freezed, json_serializable, retrofit, or auto_route annotations.
Skip this phase if no generated outputs are affected.
NEVER edit generated files (.g.dart, .freezed.dart, .gr.dart) manually.
Action: Invoke the code-generation skill for all affected files.
After code generation completes (or is skipped), invoke the feedback-loop skill on every .dart file you created or modified.
1. IF source files use code-generation annotations:
→ run code-generation skill
2. ALWAYS:
→ run feedback-loop skill on all created/modified .dart files