菜单
Run Flutter/Dart formatting and static analysis for this repository. Use after completing Dart, Flutter, generated-source-input, or project configuration changes; when the user asks to lint, format, analyze, or check code style; or when preparing code for a pull request.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | lint-format |
| description | Run Flutter/Dart formatting and static analysis for this repository. Use after completing Dart, Flutter, generated-source-input, or project configuration changes; when the user asks to lint, format, analyze, or check code style; or when preparing code for a pull request. |
| allowed-tools | Bash Read Grep Glob |
| model | claude-sonnet-4-6 |
Run this skill after completing Flutter/Dart code changes unless a broader verification skill already ran equivalent checks. Never declare code work complete with known formatting or analyzer failures.
AGENTS.mddocs/PROJECT_GUIDELINES.mdanalysis_options.yamlpubspec.yamlRun the wrapper script from the repo root:
.agents/skills/lint-format/scripts/lint-format.sh
The script auto-detects whether Flutter-relevant files changed. When relevant files changed, it formats changed Dart files and runs a project-wide analyzer pass.
Claude-discovered path:
.claude/skills/lint-format/scripts/lint-format.sh
| Flag | What it does |
|---|---|
all or --all | Format standard Dart source directories even if no changed files are detected, then analyze. |
--check | Check formatting without writing changes, then analyze. |
--format-only | Run only fvm dart format. |
--analyze-only | Run only fvm flutter analyze. |
--help | Show script usage. |
| Step | Command |
|---|---|
| Format | fvm dart format <changed Dart files> |
| Format check | fvm dart format --set-exit-if-changed <changed Dart files> |
| Analyze | fvm flutter analyze |
The default formatter target is changed non-generated Dart files. It skips generated outputs such as *.g.dart, *.freezed.dart, *.gr.dart, and lib/assets/**.
If changed annotations, routes, DTOs, localization, or asset inputs require generated files, run make gen before this skill so the analyzer sees the current generated code.
make gen when the failure points to stale generated code.fvm flutter pub get.fvm dart format and fvm flutter analyze over global Dart or Flutter commands.Task Breakdown Command. Breaks a feature into discrete, dependency-ordered implementation tasks from a PRD and tech spec. Creates a task list and individual task files with no approval prompt. When run inside the `/start-job` pipeline, return control to that orchestrator so it can invoke the implementation phase. When invoked standalone, stop after generating tasks and prompting for the next step. Use when the user says "break this down into tasks", "create tasks", "task breakdown", or after the tech spec is complete and the user wants to plan implementation.
Create a Flutter feature Product Requirements Document through a structured clarify-plan-draft workflow. Outputs a PRD using the repository template under `.claude/tasks/<feature-name>/prd.md`. Use when the user says "create a PRD", "write requirements", "define the feature", "start a feature spec", or wants to specify a feature before techspec/tasks/start-job.
Technical Specification Command. Translates a PRD into an implementation-ready technical spec through deep project analysis and clarification. Use when the user says "create a tech spec", "write the technical design", "spec this out", or after a PRD is complete and the user wants to move to technical planning.
Top-level orchestrator for Flutter feature specification. Runs the full uninterrupted pipeline: prd → techspec → tasks in one shot. Use when the user says "spec a feature", "write a spec for", "start feature spec", "plan a feature", or wants to go from idea to implementation-ready tasks without typing three separate commands.
Build/test/lint verification pass for this Flutter app — runs codegen, analyze, test, then iOS + Android native builds in parallel, then `dart format`. Does NOT commit anything; leaves the working tree dirty so the user can review and commit on demand. Used at the end of the prd → techspec → tasks → implement-tasks-sequence flow before `pr-review`, and can also be invoked manually when the user says "verify build", "run full verification", or "check everything".
Create or update a GitHub PR for this Flutter repository using gh CLI. Verifies the work with build-verify and pr-review, generates an inline PR description, commits pending changes when approved, pushes, and opens or updates the PR. Supports stacked PRs by asking for the base branch when detection is ambiguous. Use when the user says "create PR", "open PR", "push PR", or wants to submit their work for review.