dart-run-static-analysis
This skill provides workflows for executing Dart static analysis and applying automated code fixes using the Dart CLI tools.
Is dart-run-static-analysis safe to install?
Review the source first: our audit of dart-run-static-analysis's source files found 4 shell commands, 0 external URLs, file reads and writes (high risk). Every command and URL listed appears verbatim in the skill's source. The skill executes shell commands that modify source code files and reads project configuration files.
How we audit skills: our security review methodology.
Who is this skill for?
Dart and Flutter developers who want to automate code quality checks and mechanical refactoring.
What can you do with it?
- Identify type-related bugs and style violations in Dart projects.
- Apply automated fixes for outdated API usages and mechanical lint issues.
- Configure project-wide analysis rules via analysis_options.yaml.
- Suppress specific diagnostics at the file or line level.
How good is this skill?
Quality score: 5/10. The skill provides clear, actionable workflows and configuration examples for standard Dart development practices.
What does the skill file contain?
# Analyzing and Fixing Dart Code ## Contents - [Analysis Configuration](#analysis-configuration) - [Diagnostic Suppression](#diagnostic-suppression) - [Workflow: Executing Static Analysis](#workflow-executing-static-analysis) - [Workflow: Applying Automated Fixes](#workflow-applying-automated-fixes) - [Examples](#examples) ## Analysis Configuration Configure the Dart analyzer using the `analysis_options.yaml` file located at the package root. - **Base Configuration:** Always include a standard rule set (e.g., `package:lints/recommended.yaml` or `package:flutter_lints/flutter.yaml`) using t...
Frequently asked questions
How do I exclude generated files from analysis?
Add the file or directory path to the analyzer: exclude: node in your analysis_options.yaml file using glob patterns.
Can I treat info-level diagnostics as failures?
Yes, append the --fatal-infos flag to the dart analyze command.
How do I suppress a diagnostic for a single line of code?
Add // ignore: <diagnostic_code> on the line directly above the code or at the end of the line.
Related skills
flutter-apply-architecture-best-practices
21.6KFlutter developers building new projects or refactoring existing codebases for scalability
This skill provides a structured architectural framework for Flutter applications, enforcing a layered approach consisting of UI, Logic, and Data layers.
mcp-apps-builder
16.1KDevelopers building MCP servers with the mcp-use framework
A framework-specific guide for building, testing, and deploying MCP servers using the mcp-use library. It provides architectural patterns, security best practices, and CLI instructions for developers.
flutter-animations
14.4KFlutter developers who need to implement or troubleshoot motion effects within their applications
The flutter-animations skill provides guidance and code patterns for implementing, debugging, and refactoring Flutter animations. It assists with implicit animations, explicit controllers, Hero transitions, staggered sequences, and physics-based motion while enforcing accessibility and performance standards.
swift-concurrency
13.2KSwift developers managing concurrency issues, refactoring callback-based code, or migrating projects to Swift 6
The swift-concurrency skill provides diagnostic and refactoring guidance for Swift Concurrency, including migration to Swift 6, actor isolation, Sendable conformance, and task management.