文档任务可能扩展为删除仓库中的注释代码
原文依据:4 处该 Skill 的声明用途是记录文档和决策,但最终验证清单要求“不保留任何被注释掉的代码”。这是对源文件的清理要求,不只是编写文档,也没有限定到用户明确指定的文件。
如果代理把清单应用到整个仓库,可能删除暂时保留的实现、调试片段或尚未迁移的参考代码,形成持久且超出文档任务预期的文件变更。版本控制通常可恢复,但未提交内容可能丢失。
该 Skill 的主要用途是编写文档和 ADR,但其活动性验证清单要求确认“没有被注释掉的代码”,前文还明确写着“Delete it”。如果代理把这些要求应用于整个仓库,它可能在用户只要求记录文档时删除源文件中的注释代码;这些内容也可能是保留示例、临时诊断或尚未提交的用户工作。用户可要求作者将检查限定为报告问题,且仅在用户明确授权的文件中删除。
---name: documentation-and-adrsdescription: Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.---查看另外 3 个位置
After documenting:- [ ] ADRs exist for all significant architectural decisions- [ ] README covers quick start, commands, and architecture overview- [ ] API functions have parameter and return type documentation- [ ] Known gotchas are documented inline where they matter- [ ] No commented-out code remains- [ ] Rules files (CLAUDE.md etc.) are current and accurate// Don't leave commented-out code// const oldImplementation = () => { ... } ← Delete it, git has history```## VerificationAfter documenting:- [ ] ADRs exist for all significant architectural decisions- [ ] README covers quick start, commands, and architecture overview- [ ] API functions have parameter and return type documentation- [ ] Known gotchas are documented inline where they matter- [ ] No commented-out code remains- [ ] Rules files (CLAUDE.md etc.) are current and accurate