Dart Tooling Agent Skill

Dart static analysis, linting, formatting, and code-generation standards. Use only for analysis_options.yaml, build_runner, dart format, DCM, lefthook, or analyze/format CI failures; defer Dart language, null-safety, Flutter tests, and generic CI questions.

1k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

536

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill dart-tooling

What comes with it

2 669 bytes besides the instruction

evals/evals.json

The instruction itself

6 sections, as written by the author

Tooling & CI

Priority: P1 (HIGH)

Implementation Guidelines

Linter: Use analysis_options.yaml. Enforce always_use_package_imports and require_trailing_commas.
Formatting: Use dart format . --line-length 80. Run on every commit.
DCM: Use dart_code_metrics for complexity checks (Max cyclomatic complexity: 15).
Build Runner: Always use --delete-conflicting-outputs with code generation.
CI Pipeline: All PRs MUST pass analyze, format, and test steps.
Imports: Group imports: dart:, package:, then relative.
Documentation: Use /// for public APIs. Link symbols using [Class].
Linting Commands:
flutter analyze --fatal-infos --fatal-warnings
dart run dart_code_metrics:metrics analyze lib
Pre-commit: Keep lefthook.yml in sync with analyze/format/metrics commands.

Code

# analysis_options.yaml
analyzer:
  errors:
    todo: ignore
    missing_required_param: error
linter:
  rules:
    - prefer_single_quotes
    - unawaited_futures

Anti-Patterns

No build_runner without --delete-conflicting-outputs: Causes stale generated file conflicts that break compilation.
No flutter build before flutter analyze: Analyze fast; always fail fast before building.
No ignore comment without explanation: Always annotate why lint ignore justified.
No skipping dart format in pre-commit: Unformatted code breaks CI; enforce via lefthook.yml.

References

language | testing

Other skills for the same job

different authors, same section of the catalogue

Receiving Code Review

by ZhanlinCui

×7

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

2k tokens

Requesting Code Review

by ZhanlinCui

×6

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Comprehensive GitHub code review with AI-powered swarm coordination

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens

How to use it

Copy the folder

Take hoangnguyen0403/dart-tooling from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.