使用方法
- 复制安装命令，在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物，并对照来源检查输出。
npx skills add https://github.com/emiliodominguez/flow-skills --skill flow-simplify开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况，不等于独立质量或安全测试。
按源仓库内容呈现，保留标题、案例、代码、表格、链接以及原文引用的演示图片。
Simplify
Subtract only where it improves understanding without changing required behavior. Fewer lines is a possible outcome, not the acceptance criterion.
Process
- Bound the cleanup, establish relevant checks and preserve unrelated staged/unstaged work.
Name the concrete complexity: dead paths, needless indirection, duplicate responsibility, stale comments or generated slop.
- Order reduction passes by semantic risk. For large scopes, authorized read-only reviewers can
inspect disjoint areas; one writer per file. No arbitrary agent or file-count threshold.
- Caller-check before deleting a symbol: imports, dynamic lookup, registries, reflection,
routes, config, templates, tests, generated sources, package exports. Repository search cannot see external consumers of a published API.
- Mark a deletion CONFIRMED-DEAD only with usage and runtime evidence; keep uncertain
exports or negotiate the compatibility change. Keep side-effect imports (registration, polyfills) and license, compiler and tool-directive comments.
- Inspect single-use abstractions instead of auto-inlining. Components, Hooks, closures and
effects carry identity, state lifetime and evaluation order even with one caller.
- Remove a defensive guard only when input provenance proves it redundant. Static types do not
validate network, JSON, storage, DOM or JavaScript consumers.
- Cut in small steps, run behavior and repository checks, inspect the combined diff. Stop when
the stated complexity is resolved.
Anti-patterns
- Net-negative lines as a quality gate, or every single-use component as waste.
- Removing imports, comments or guards on regex or type evidence alone.
- Deleting a public export because internal grep finds no caller.
- Quietly changing error behavior or component state lifetime.
Done when
- The targeted code is easier to understand with semantics and compatibility preserved.
- Deletions have evidence; uncertain consumers remain explicit.
- Required checks ran on the resulting artifact, not an earlier baseline.
Use flow-review for the diff or flow-refactor for a separate ownership or structure problem.
