Rule migration deletes content judged obsolete, duplicated, or too host-specific
Source references: 2The workflow explicitly splits rules from `CLAUDE.md` and deletes content judged obsolete, duplicated, or overly tied to a host. Although it requires describing deletions before writing, it does not require a backup, a complete diff, or tests showing that the rules are no longer needed.
A mistaken judgment could permanently remove necessary project constraints, security restrictions, or Claude-specific operating instructions, causing later Agent behavior to diverge from project requirements.
The risk is supported. The workflow actively calls for deleting rules the model judges obsolete, duplicated, or too host-specific; a mistaken judgment could remove safeguards, project conventions, or required host settings. It must disclose proposed deletions before writing, which adds visibility, but the source does not require a backup, item-by-item approval, a retained diff, or post-deletion behavioral tests. Users can require a full diff, approve each deletion, and keep a recoverable copy.
如果有 `CLAUDE.md`:- 拆出平台无关规则 → 写入 `AGENTS.md`- 保留 Claude 专属规则在 `CLAUDE.md`- 删除过时、重复、宿主绑定太强的内容Show 1 other places
#### Phase 2 写入前确认写入前必须明确告诉用户:- 这次要新建还是改写哪个文件- 会保留什么- 会删除什么- 为什么这样分层