使用方法
- 复制安装命令，在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物，并对照来源检查输出。
npx skills add https://github.com/thiennc-tesoglobal/flutter-skills --skill flutter-code-review开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况，不等于独立质量或安全测试。
按源仓库内容呈现，保留标题、案例、代码、表格、链接以及原文引用的演示图片。
Flutter Code Review
Find defects that materially affect behavior, users, delivery, or maintainability. A review is an evidence-backed risk assessment, not a style tour or an implicit rewrite.
Establish the review boundary
- Determine the requested diff, commit range, pull request, working tree, or module and the intended behavior.
- Read repository instructions and inspect enough nearby code, tests, generated boundaries, and configuration to understand changed behavior.
- Review changed lines first, but follow their data flow and lifecycle when evidence requires surrounding context.
- Do not edit files, post comments, approve, merge, or expand into remediation unless the user authorizes those actions.
Review by risk
Prioritize data loss, security exposure, crashes, incorrect results, broken lifecycle, concurrency races, inaccessible flows, release failures, and missing regression coverage. Then consider architecture or maintainability issues that have a concrete cost.
Do not report preferences, hypothetical rewrites, unchanged legacy issues, or framework behavior that current code already handles. Validate API and package claims against the project's SDK and resolved dependencies.
Load references conditionally
- Read review workflow for gathering the change, tracing impact, calibrating severity, and formatting findings.
- Read Flutter review checklist only for the technical domains touched by the change.
Load available specialists only when their domain is materially changed or a claim needs deeper verification. A review touching storage does not automatically require every quality skill.
Output
Lead with findings ordered by severity. Each finding must name the affected file and tight line range, explain the failure path and impact, and propose a proportionate correction. Keep separate sections for open questions and a short summary only when useful.
If there are no actionable findings, say so directly and identify meaningful verification gaps. Never invent findings to make the review appear thorough.
