Skip to content
cccskills
FreePublished on GitHub

lint-format

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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md2.8 KB
  • scripts/lint-format.sh5.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Flutter Template Lint and Format

MANDATORY

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.

Read First

  • AGENTS.md
  • docs/PROJECT_GUIDELINES.md
  • analysis_options.yaml
  • pubspec.yaml

Usage

Run 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

Flags

FlagWhat it does
all or --allFormat standard Dart source directories even if no changed files are detected, then analyze.
--checkCheck formatting without writing changes, then analyze.
--format-onlyRun only fvm dart format.
--analyze-onlyRun only fvm flutter analyze.
--helpShow script usage.

What It Runs

StepCommand
Formatfvm dart format <changed Dart files>
Format checkfvm dart format --set-exit-if-changed <changed Dart files>
Analyzefvm 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.

Feedback Loop

  1. Run the script.
  2. If formatting changed files, inspect the diff.
  3. If analyzer failures appear, fix the underlying source issue.
  4. Run make gen when the failure points to stale generated code.
  5. Re-run the script until all checks pass.
  6. Only then declare work complete.

Prerequisites

  • FVM installed and configured for the repo.
  • Dependencies fetched with fvm flutter pub get.
  • Generated files are current when the change touched codegen inputs.

Rules

  • Prefer fvm dart format and fvm flutter analyze over global Dart or Flutter commands.
  • Do not hand-edit generated files to satisfy the analyzer.
  • Do not run platform-native Swift, Gradle, Spotless, Detekt, or KMP checks from this skill.
  • Do not stage or commit formatting changes automatically.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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".

The English summary is being prepared. Showing the original description.

strvcom/flutter-template24Updated Jun 18, 2026

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.

The English summary is being prepared. Showing the original description.

strvcom/flutter-template24Updated Jun 18, 2026

Build a full feature in this Flutter repository that includes backend or storage data flow: read API schema, create DTOs, map DTOs to entities, add Riverpod use cases, connect feature state, and render UI data. Use when a task goes beyond a screen and needs real data integration.

The English summary is being prepared. Showing the original description.

strvcom/flutter-template24Updated Jun 18, 2026

Create a new Flutter screen in this repository using the existing feature structure, AutoRoute setup, Riverpod state pattern, and code generation workflow. Use when adding a new page, route, stateful screen, or feature folder in this template.

The English summary is being prepared. Showing the original description.

strvcom/flutter-template24Updated Jun 18, 2026

Implement a single Flutter task following this repository's Riverpod, Freezed, AutoRoute, DTO/entity, codegen, and verification conventions. Reads the task definition, PRD, and tech spec, then executes the implementation. When invoked standalone, verifies the change; when invoked by implement-tasks-sequence, writes code only and leaves verification to start-job/build-verify. Use when the user says "implement task X", "work on task X", or wants to execute a specific task from the task list.

The English summary is being prepared. Showing the original description.

strvcom/flutter-template24Updated Jun 18, 2026

Orchestrates implementation of all tasks for a feature using an agent team. Respects task dependencies, runs tasks in correct order, parallelizes independent tasks. Does NOT build, run tests, or commit at any point — verification is delegated to the caller (typically `/start-job`, which runs `build-verify` and `pr-review uncommitted` afterwards). Use when the user says "implement all tasks", "run the task sequence", "implement the feature", or wants to execute multiple tasks from a task list end-to-end.

The English summary is being prepared. Showing the original description.

strvcom/flutter-template24Updated Jun 18, 2026

See all skills by strvcom

Report a problem with this skill