スキル dart-fix-runtime-errors
📦
dart-fix-runtime-errors
コンテンツリビジョン r1 安全 ⚙️ 外部コマンド
Resolve Dart Runtime Errors Safely
Dart type and null-safety errors can delay development and cause runtime failures. This skill provides a structured workflow to analyze, fix, and verify local Dart code changes.
対応: Claude Codex Code(CC)
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
エージェントリクエスト
Review the Skillstore skill "dart-fix-runtime-errors" from https://skillstore.io/skills/flutter-dart-fix-runtime-errors.md and its manifest at https://skillstore.io/api/skills/flutter-dart-fix-runtime-errors/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「dart-fix-runtime-errors」を使用しています。 A List<dynamic> cannot be passed to a method expecting List<int>.
期待される結果:
- Identify the inferred dynamic collection.
- Create the collection with an explicit int type.
- Run Dart analysis and tests to verify the change.
「dart-fix-runtime-errors」を使用しています。 A non-nullable instance field is not initialized.
期待される結果:
- Check whether the field can be nullable.
- Use a constructor initializer when possible.
- Use late only when initialization before every read is guaranteed.
セキュリティ監査
安全v1 • 2026/8/30 バージョン別レポートを開く
All 50 static findings are false positives. The analyzer misread Markdown code delimiters, fixed Dart commands, and Dart examples as shell execution or system reconnaissance. The skill contains a local workflow for Dart analysis and testing, with no prompt injection, data collection, network activity, or command construction from user input.
1
スキャンされたファイル
167
解析済み行数
0
レビュー項目
0
誤検知を無視
リスク要因
⚙️ 外部コマンド (35)
SKILL.md:24 SKILL.md:25 SKILL.md:26 SKILL.md:27 SKILL.md:32 SKILL.md:33 SKILL.md:34 SKILL.md:39 SKILL.md:40 SKILL.md:41 SKILL.md:57-59 SKILL.md:59-62 SKILL.md:62-63 SKILL.md:63-68 SKILL.md:68-75 SKILL.md:75 SKILL.md:76-79 SKILL.md:79 SKILL.md:82-86 SKILL.md:86-89 SKILL.md:89-90 SKILL.md:90-91 SKILL.md:91 SKILL.md:97-106 SKILL.md:106-109 SKILL.md:109-118 SKILL.md:118-122 SKILL.md:122-131 SKILL.md:131-134 SKILL.md:134-143 SKILL.md:143-145 SKILL.md:145-147 SKILL.md:147-155 SKILL.md:155-158 SKILL.md:158-166
最新の完了済み静的・セマンティック監査では、確認済みのセキュリティ検出事項は見つかりませんでした。これは、スキルに副作用がないことを証明するものではありません。
監査者: claude
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/flutter-dart-fix-runtime-errors/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/flutter-dart-fix-runtime-errors?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/flutter-dart-fix-runtime-errors?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/flutter-dart-fix-runtime-errors/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/flutter-dart-fix-runtime-errors.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-fix-runtime-errors security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/flutter-dart-fix-runtime-errors/audits/1BibTeX形式の引用
@techreport{flutter-flutter-dart-fix-runtime-errors-2026,
author = {flutter},
title = {dart-fix-runtime-errors security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/flutter-dart-fix-runtime-errors/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-fix-runtime-errors 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-fix-runtime-errors/audits/1"
identifiers:
- type: other
value: "skillstore:flutter-dart-fix-runtime-errors:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中 55
アーキテクチャ
85
保守性
85
コンテンツ
65
コミュニティ
83
仕様準拠
作成できるもの
Fix a null-safety error
Identify nullable values and select a safe initialization, optional access, or fallback strategy.
Resolve collection type errors
Add explicit generic types when analyzer output reports incompatible dynamic collections.
Verify a team code change
Run analysis and tests after a fix before submitting a pull request.
これらのプロンプトを試す
Analyze my project
Run Dart static analysis for this project. Explain the first errors and propose minimal fixes.
Fix null safety
Help me resolve this Dart null-safety error. Explain whether optional access, a fallback, or initialization is appropriate.
Correct type mismatch
Investigate this Dart type mismatch. Trace the inferred types and propose an explicit, safe type annotation.
Verify a complete fix
Review my Dart error fix. Run static analysis and tests, summarize results, and identify any remaining failures.
ベストプラクティス
- Run dart fix with dry-run before applying changes.
- Prefer explicit types and constructor initialization over unsafe casts or late fields.
- Run dart analyze and dart test after every fix.
回避
- Do not apply automated fixes without reviewing the proposed changes.
- Do not use a null assertion when a value can be absent.
- Do not silence analyzer errors with broad casts that hide invalid runtime types.
よくある質問
What errors does this skill address?
It addresses common Dart static analysis errors involving types, null safety, generics, and method overrides.
Does it change my files automatically?
It can guide dart fix usage. Review the dry-run output before applying changes.
Should I use late for every uninitialized field?
No. Use late only when every code path initializes the field before it is read.
Why run dart analyze after dart fix?
Automated fixes do not resolve every issue. Analysis identifies remaining errors.
Why run tests after static analysis passes?
Tests can reveal behavior problems that static analysis does not cover.
Does this skill fix all Flutter errors?
No. It focuses on Dart analysis issues, not all platform, build, or deployment errors.