Back to Details

changeset

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

changeset — File Impact & Cascade Planning

Changeset — 文件影响与级联规划

Domain Rubric

领域准则

Input & Boundary

输入与边界

Receive a settled direction or solution with outcome, constraints, and available evidence. Ground it against the current checkout and governing contracts; keep planning read-only and preserve the supplied direction.
Trace direct and indirect callers, implementations, imports, schemas, and tests. Inspect only the target and load-bearing cascades; exclude cosmetic churn, speculative files, and unaffected backward-compatible callers. Prune superseded logic: stage explicit removal of dead helpers, obsolete branches, and tests invalidated by the solution. Stop if the input plan is stale or contradictory rather than silently redesigning it.
接收一个已确定的方向或解决方案，其中包含预期结果、约束条件和可用证据。以当前 checkout 和适用契约为依据进行核实；保持规划过程只读，并遵循所提供的方向。
追踪直接和间接调用方、实现、导入、schema 与测试。仅检查目标范围和关键依赖级联；排除表层改动、推测性文件以及不受影响且保持向后兼容的调用方。清理被取代的逻辑：明确安排移除无用的辅助函数、过时分支，以及因该解决方案而失效的测试。如果输入计划已过时或自相矛盾，应停止，而不是在未说明的情况下重新设计。

File Actions

文件操作

  • [CREATE]
    : New file required by the solution.
  • [MOVE]
    : Relocation or rename, including affected references.
  • [UPDATE]
    : Existing logic, contract, test, or necessary cascade.
  • [DELETE]
    : Obsolete file whose removal is required by the solution.
  • [CREATE]
    ：解决方案所需的新文件。
  • [MOVE]
    ：迁移或重命名，包括受影响的引用。
  • [UPDATE]
    ：现有逻辑、契约、测试或必要的级联变更。
  • [DELETE]
    ：解决方案要求移除的过时文件。

State

状态

  • STAGED
    : The Changeset Tree identifies concrete operations and necessary cascades for the settled direction.
  • UNRESOLVED
    : Missing, stale, or conflicting direction prevents a reliable changeset; cite the blocker and decision required.
  • STAGED
    ：
    Changeset Tree
    已确定既定方向所需的具体操作和必要级联变更。
  • UNRESOLVED
    ：缺失、过时或相互冲突的方向导致无法可靠生成 changeset；应说明阻塞项和所需决策。

Canonical Output Contract

规范输出契约

markdown
undefined
markdown
undefined

Changeset: <Scope> · STAGED

Changeset: <Scope> · STAGED

Basis: <Settled solution and supporting proof/reference.> Acceptance: <Observable criteria and constraints to carry downstream.>
text
|-- <subsystem>/
|   |-- <file>
|   |   `-- [UPDATE] <Load-bearing change and invariant>.
|   `-- <new-file>
|       `-- [CREATE] <Required component or regression check>.
`-- <deep/path/to/caller>
    `-- [UPDATE] <Necessary cascade>.

Summary: <N> files affected (<C> created, <U> updated, <M> moved, <D> deleted).

For `UNRESOLVED`, replace the tree with a concise blocker, evidence, and required redesign decision; omit invented file operations.
Basis: <Settled solution and supporting proof/reference.> Acceptance: <Observable criteria and constraints to carry downstream.>
text
|-- <subsystem>/
|   |-- <file>
|   |   `-- [UPDATE] <Load-bearing change and invariant>.
|   `-- <new-file>
|       `-- [CREATE] <Required component or regression check>.
`-- <deep/path/to/caller>
    `-- [UPDATE] <Necessary cascade>.

Summary: <N> files affected (<C> created, <U> updated, <M> moved, <D> deleted).

对于 `UNRESOLVED`，请将树替换为简洁的阻塞项、证据和所需重新设计决策；不要虚构文件操作。

Routing

路由

  • An outdated plan exposes unresolved requirements → (via /clarify).
  • An outdated plan requires a new design direction → (via /architect-decision).
  • The supported changeset is authorized for implementation → (via /forge).
  • The caller wants task decomposition into verifiable slices → (via /split-tasks).
  • The caller wants backlog persistence or issue tracking → (via /tracking-tasks).
  • 过时的计划暴露出尚未解决的需求 →（通过 /clarify）。
  • 过时的计划需要新的设计方向 →（通过 /architect-decision）。
  • 受支持的 changeset 已获准实施 →（通过 /forge）。
  • 调用方希望将任务拆分为可验证的切片 →（通过 /split-tasks）。
  • 调用方希望持久化 backlog 或进行 issue 跟踪 →（通过 /tracking-tasks）。

Execution Protocol

执行协议

  1. Inspect the supplied direction and current code/contracts. Stop on an outdated plan or foundational contradiction and report 
    UNRESOLVED
    with the required redesign decision.
  2. Build the tree with file actions, direct cascades, acceptance criteria, and evidence provenance. Collapse redundant directories while preserving file hierarchy.
  3. Present 
    STAGED
    and halt without filesystem mutations. An embedded changeset produced elsewhere uses the same handoff obligations without requiring this skill.
  1. 检查所提供的方向以及当前代码和契约。如果计划过时或存在根本性矛盾，则停止，并报告 
    UNRESOLVED
    以及所需的重新设计决策。
  2. 构建 changeset 树，其中包含文件操作、直接级联、验收标准和证据来源。合并冗余目录，同时保留文件层级。
  3. 呈现 
    STAGED
    状态并停止，不对文件系统进行任何变更。在其他位置生成的嵌入式 changeset 应遵循相同的交接要求，无需使用此 skill。