์Šคํ‚ฌ 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)
Maintain this Skill? Claim it ๐Ÿฅ‰ 77 ๋ธŒ๋ก ์ฆˆ

๋‚ด ์—์ด์ „ํŠธ๋กœ ์„ค์น˜

์ด ์š”์ฒญ์„ ์—์ด์ „ํŠธ์— ๋ณต์‚ฌํ•˜์„ธ์š”. ๊ณต์‹ 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.

๋ณด์•ˆ ๊ฐ์‚ฌ

์•ˆ์ „

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_report

Markdown ๋ฐฐ์ง€

[![Skillstore security assessment](https://skillstore.io/badges/skills/flutter-dart-run-static-analysis/security.svg)](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/1

BibTeX ์ธ์šฉ

@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.

๊ฐœ๋ฐœ์ž ์„ธ๋ถ€ ์ •๋ณด

์ž‘์„ฑ์ž

flutter

๋ผ์ด์„ ์Šค

MIT

Skillstore ๋ฆฌ๋น„์ „

r1

๋ฒ„์ „ ์•ˆ๋‚ด

์ž‘์„ฑ์ž๊ฐ€ ๋ฒ„์ „์„ ์„ ์–ธํ•˜์ง€ ์•Š์•˜์Šต๋‹ˆ๋‹ค.

์ฐธ์กฐ

5fe3b354432749df6b19785dd9af3a0cf113b517

์œ ์ง€๋ณด์ˆ˜ ์ตœ์‹ ์„ฑ

2026. 8. 31.

์‚ฌ์šฉ๋Ÿ‰

1 ๋‹ค์šด๋กœ๋“œ ยท 0 ์กฐํšŒ

ํŒŒ์ผ ๊ตฌ์กฐ

๐Ÿ“„ SKILL.md