スキル dart-run-static-analysis
📦
dart-run-static-analysis
コンテンツリビジョン r1 安全 ⚙️ 外部コマンド
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.
対応: Claude Codex Code(CC)
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
エージェントリクエスト
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.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「dart-run-static-analysis」を使用しています。 Analyze this Flutter package before I commit.
期待される結果:
- 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.
「dart-run-static-analysis」を使用しています。 Preview automated Dart fixes without changing files.
期待される結果:
- 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.
セキュリティ監査
安全v1 • 2026/8/30 バージョン別レポートを開く
All 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.
1
スキャンされたファイル
105
解析済み行数
0
レビュー項目
0
誤検知を無視
リスク要因
最新の完了済み静的・セマンティック監査では、確認済みのセキュリティ検出事項は見つかりませんでした。これは、スキルに副作用がないことを証明するものではありません。
監査者: claude
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/flutter-dart-run-static-analysis/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/flutter-dart-run-static-analysis?utm_source=security_passport_badge)HTMLバッジ
<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>埋め込みカード
<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>学術引用 (APA · BibTeX · CFF)
APA形式の引用
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形式の引用
@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 スコア
このスコアの理由 証拠の信頼度: 中 55
アーキテクチャ
85
保守性
87
コンテンツ
65
コミュニティ
83
仕様準拠
作成できるもの
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.
これらのプロンプトを試す
Run a basic analysis
Run Dart static analysis for this project. Summarize each diagnostic and suggest the safest next step.
Fix reported lints
Run dart analyze, group the diagnostics by cause, and show which fixes are mechanical before changing files.
Preview automated fixes
Run dart fix --dry-run for this package. Explain the proposed changes and wait for my approval before applying them.
Harden analyzer settings
Review analysis_options.yaml and propose strict type checks and lint rules. Explain each change and preserve existing project-specific rules.
ベストプラクティス
- 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.
回避
- 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.
よくある質問
What does this skill run?
It guides use of dart analyze, dart fix, and dart format for Dart and Flutter projects.
Will it change my files automatically?
It recommends a dry run first. Applying fixes changes files only when the requested command is approved and run.
Can it configure Flutter lint rules?
Yes. It explains how to configure analysis_options.yaml, including flutter_lints and strict analyzer settings.
Can I use it with a pure Dart package?
Yes. The analysis and fix workflow applies to Dart packages, not only Flutter applications.
Does it fix every diagnostic?
No. dart fix only supports certain mechanical changes. Other diagnostics need manual investigation and edits.
Does a clean analysis replace testing?
No. Static analysis complements unit tests, integration tests, and human code review.