dart-run-static-analysis
Improve Dart Code with Static Analysis
Dart diagnostics can be difficult to review and resolve before a commit. This skill guides Claude Code, Claude, and Codex through analysis, reviewed fixes, and formatting.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "dart-run-static-analysis" from https://skillstore.io/skills/flutter-dart-run-static-analysis.md and its manifest at https://skillstore.io/api/skills/flutter-dart-run-static-analysis/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "dart-run-static-analysis". Analyze this Flutter package before I commit.
Expected outcome:
- Analysis completed with diagnostics grouped by error, warning, and info level.
- Recommended fixes identify affected files and explain which changes require manual review.
- A final verification step reruns analysis after approved changes.
Using "dart-run-static-analysis". Preview automated Dart fixes without changing files.
Expected outcome:
- Dry-run results list the proposed mechanical fixes.
- The response highlights changes that may affect APIs or formatting.
- No files are changed until the user approves applying fixes.
Security Audit
SafeAll 24 static findings are false positives. The external-command matches are Markdown formatting around documented Dart CLI commands and configuration, not executable code. The remaining reconnaissance match is an ordinary local Dart example, and no prompt injection, exfiltration, or malicious intent was found.
Risk Factors
⚙️ External commands (23)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/flutter-dart-run-static-analysis/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/flutter-dart-run-static-analysis?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/flutter-dart-run-static-analysis?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/flutter-dart-run-static-analysis/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/flutter-dart-run-static-analysis.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
flutter. (2026). dart-run-static-analysis security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/flutter-dart-run-static-analysis/audits/1BibTeX citation
@techreport{flutter-flutter-dart-run-static-analysis-2026,
author = {flutter},
title = {dart-run-static-analysis security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/flutter-dart-run-static-analysis/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "dart-run-static-analysis security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "flutter"
date-released: "2026-08-30"
url: "https://skillstore.io/skills/flutter-dart-run-static-analysis/audits/1"
identifiers:
- type: other
value: "skillstore:flutter-dart-run-static-analysis:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Prepare a Flutter change for review
Run analysis, inspect diagnostics, and format a Flutter change before opening a pull request.
Configure stricter Dart diagnostics
Set up analysis_options.yaml with recommended rules and strict type checks for a Dart package.
Modernize a Dart codebase
Preview and review supported automated fixes during a Dart SDK or API migration.
Try These Prompts
Run Dart static analysis for this project. Summarize each diagnostic and suggest the safest next step.
Run dart analyze, group the diagnostics by cause, and show which fixes are mechanical before changing files.
Run dart fix --dry-run for this package. Explain the proposed changes and wait for my approval before applying them.
Review analysis_options.yaml and propose strict type checks and lint rules. Explain each change and preserve existing project-specific rules.
Best Practices
- Run dart analyze before committing or submitting a review.
- Use dart fix --dry-run and review the proposed changes before applying them.
- Keep analysis_options.yaml under version control with project-specific rules documented.
Avoid
- Do not apply automated fixes without reviewing the dry-run output.
- Do not suppress diagnostics broadly when a targeted fix is practical.
- Do not treat a clean analysis run as a substitute for tests and code review.