Post-generation workflow that orchestrates code generation and quality verification for created or modified Dart files.
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.
Create a new reusable component in module_ui (modules/ui/lib/uikit) with proper theming, asset access, naming, exports, golden test, and Figma mapping update. Use when adding a new design system component shared across features.