Executa `dart analyze` para identificar avisos e erros, e usa `dart fix --apply` para resolver automaticamente problemas de lint mecânicos. Use durante o desenvolvimento para garantir a qualidade do código e antes de confirmar alterações.
Esta habilidade automatiza a análise estática de código Dart usando as ferramentas oficiais `dart analyze` e `dart fix --apply`. Ela é útil para desenvolvedores que desejam manter a qualidade do código, detectar erros e avisos de forma proativa e corrigir automaticamente problemas de lint mecânicos antes de confirmar alterações. A habilidade suporta projetos Dart e Flutter, funcionando em qualquer ambiente que tenha o SDK Dart instalado. Ao executar, ela primeiro identifica problemas com `dart analyze`, então aplica correções automáticas com `dart fix --apply`, garantindo que o código esteja limpo e consistente. É recomendada para uso durante o desenvolvimento e como parte do fluxo de trabalho de pré-confirmação (pre-commit).
npx skills add https://github.com/dart-lang/skills/tree/main/skills/dart-run-static-analysisInstalled? Explore more Pesquisa e Análise de Dados skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
Execute dart analyze para identificar avisos e erros, e use dart fix --apply para resolver automaticamente problemas de lint mecânicos. Use durante o desenvolvimento para garantir a qualidade do código e antes de confirmar alterações.
This repo contains 8 individual skills — each has its own dedicated page.
Write and organize unit tests for functions, methods, and classes using `package:test`. Use when creating new logic or fixing bugs to ensure code remains correct and regression-free.
Entrypoint structure, exit codes, cross-platform scripts. Use when building command line utilities, scripts, or applications.
Collect coverage using the coverage packge and create an LCOV report
Uses get_runtime_errors and lsp to fetch an active stack trace, locate the failing line, apply a fix, and verify resolution via hot_reload.
Define and generate mock objects for external dependencies using `package:mockito` and `build_runner`. Use when unit testing classes that depend on complex external services like APIs or databases.
Replace the usage of `expect` and similar functions from `package:matcher` to `package:checks` equivalents.
Workflow for fixing package version conflicts. Use this when `pub get` fails due to incompatible package versions.
Use switch expressions and pattern matching where appropriate
USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Agent skill repository discovered by 10x-chat research.
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.