| | |
| | | # Apptag Project Rules |
| | | |
| | | 本项目 Hermes 必须严格遵守的规则 |
| | | Authoritative workflow standard: |
| | | |
| | | ## 版本管理 & 需求记录铁律(每次任务都必须执行) |
| | | - `Docs/ProjectManagement/Apptag_Development_Workflow_Standard_v1.0.md` |
| | | |
| | | 1. 任何修改文件前,必须先执行 checkpoint: |
| | | git add -A && git commit -m "checkpoint: [本次任务简要描述]" |
| | | 2. 任务完成后,**必须**更新 DECISIONS.md: |
| | | - 在文件最顶部追加一节新内容(使用当前日期) |
| | | - 格式必须严格遵守下面的模板 |
| | | 3. 最后执行正式 commit: |
| | | git add DECISIONS.md .hermes.md && git commit -m "docs: 更新 DECISIONS.md [任务描述]" |
| | | 4. 如果是重大功能,自动推送 GitHub PR(可选) |
| | | Hermes and any coder working in this repository must follow that document as the single workflow authority. |
| | | |
| | | ## 上下文管理规则 |
| | | |
| | | - 每完成 5 个任务后,自动执行一次上下文压缩 |
| | | - 压缩完成后,在 DECISIONS.md 里新增一节 “压缩摘要” |
| | | |
| | | ## |
| | | |
| | | If a task request conflicts with the workflow standard, the coder must pause, cite the exact violated clause, and resolve the conflict before proceeding. |