Menu
Verification and quality assurance feedback loop. Runs auto-fix, static analysis, and iterates until all errors are resolved.
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.
Based on SOC occupation classification
| name | feedback-loop |
| description | Verification and quality assurance feedback loop. Runs auto-fix, static analysis, and iterates until all errors are resolved. |
Run automated fixes and static analysis iteratively until zero errors remain.
Critical rule: DO NOT STOP until all errors are resolved.
You MUST use ONLY the following commands during verification. Do NOT call underlying tools directly.
| Action | Command | Notes |
|---|---|---|
| Autofix (scoped) | make autofix-scope DIR=<package_dir> SCOPE=<relative_path> | Runs both dart fix and dcm fix in the specified package |
| Analyze (scoped) | make analyze-scope DIR=<package_dir> SCOPE=<relative_path> | Runs both dart analyze and dcm analyze in the specified package |
DIR — package directory from project root (e.g. apps/main, modules/datasource/network)SCOPE — path relative to the package directory (e.g. lib/feature/app/app.dart, lib/feature/app). Defaults to lib.FORBIDDEN — never call these directly:
dart analyze / fvm dart analyzedcm analyze / dcm fixfvm dart fixThe make wrappers ensure consistent flags and tool ordering. Always use them.
For each target file (newly created or modified *.dart files):
REPEAT:
1. make autofix-scope DIR=<package_dir> SCOPE=<relative/path/to/file.dart>
2. make analyze-scope DIR=<package_dir> SCOPE=<relative/path/to/file.dart>
3. IF errors persist after autofix → fix manually, then GOTO 1
4. CONTINUE until zero errors
Escalation: If the same error persists after 3+ manual fix attempts, document as blocker.
### Verification Results
**Files verified:** {count}
**Iterations:** {number}
| File | Iterations | Status |
|------|------------|--------|
| path/to/file.dart | 2 | PASSED |
**Manual fixes:** {list if any}
**Final status:** PASSED / BLOCKED
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.