groove-daily-end

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

groove-daily-end

Outcome

输出结果

The workday is wrapped up: git changes are analysed, memory files are written in order, tasks are analysed, an end task is created, and changes are committed based on per-component git strategy.

工作日已完成收尾：分析git变更，按顺序写入记录文件，分析任务，创建收尾任务，并根据各组件的git策略提交变更。

Acceptance Criteria

验收标准

Git memory file written at
```
<memory>/git/YYYY-MM-DD-GIT-N.md
```
Daily memory file written at
```
<memory>/daily/YYYY-MM-DD.md
```
Weekly memory file written if today is the last weekday of the week
Monthly memory file written if today is the last weekday of the month
Tasks are analysed and summary is included in daily memory
End task is created in configured backend (if
```
tasks != none
```
) with status
```
in-progress
```
Changes committed for any component whose git strategy allows it

Git记录文件写入路径为
```
<memory>/git/YYYY-MM-DD-GIT-N.md
```
每日记录文件写入路径为
```
<memory>/daily/YYYY-MM-DD.md
```
若今日为当周最后一个工作日，写入周度记录文件
若今日为当月最后一个工作日，写入月度记录文件
分析任务并将摘要纳入每日记录中
若
```
tasks != none
```
，则在配置的后端中创建状态为
```
in-progress
```
的收尾任务
对于git策略允许提交的所有组件，提交其变更

Constraints

约束条件

Read
```
.groove/index.md
```
for
```
tasks:
```
,
```
memory:
```
, and
```
git.*
```
config
Memory population order (must follow this sequence):
1. ```
/groove-utilities-memory-log-git
```
2. ```
/groove-utilities-memory-log-daily
```
3. ```
/groove-utilities-memory-log-weekly
```
  (only if last weekday of week, or explicit request)
4. ```
/groove-utilities-memory-log-monthly
```
  (only if last weekday of month, or explicit request)
Call
```
/groove-utilities-task-analyse
```
to get task summary for daily memory population
Create end task via
```
/groove-utilities-task-create
```
if
```
tasks != none
```
(title
```
YYYY-MM-DD End
```
)
- User marks this task done when they're finished — do not auto-complete
Do NOT archive tasks during end — that is user-triggered only
Git commit strategy (per component):
- ```
git.memory: ignore-all
```
  — do not stage memory files
- ```
git.memory: hybrid
```
  — stage
```
<memory>/
```
  files (sessions are gitignored, logs are committed)
- ```
git.memory: commit-all
```
  — stage
```
<memory>/
```
  files
- ```
git.tasks: commit-all
```
  — stage
```
.groove/tasks/
```
  files
- ```
git.hooks: commit-all
```
  — stage
```
.groove/hooks/
```
  files
- If any files were staged: commit with message
```
YYYY-MM-DD end
```
- If nothing to stage: skip commit silently
Last weekday detection: use local calendar date; handle gracefully if run on weekend
After all standard steps: check if
```
.groove/hooks/end.md
```
exists
- If it exists: read the
```
## Actions
```
  section and execute each item in order; report completion per item
- If it does not exist: skip silently

读取
```
.groove/index.md
```
获取
```
tasks:
```
、
```
memory:
```
和
```
git.*
```
配置
记录填充顺序（必须遵循此顺序）：
1. ```
/groove-utilities-memory-log-git
```
2. ```
/groove-utilities-memory-log-daily
```
3. ```
/groove-utilities-memory-log-weekly
```
  （仅当为周度最后一个工作日或显式请求时执行）
4. ```
/groove-utilities-memory-log-monthly
```
  （仅当为月度最后一个工作日或显式请求时执行）
调用
```
/groove-utilities-task-analyse
```
获取任务摘要，用于填充每日记录
若
```
tasks != none
```
，通过
```
/groove-utilities-task-create
```
创建收尾任务（标题为
```
YYYY-MM-DD End
```
）
- 由用户标记该任务完成——请勿自动完成
收尾过程中请勿归档任务——仅可由用户触发归档操作
Git提交策略（按组件）：
- ```
git.memory: ignore-all
```
  ——不暂存记录文件
- ```
git.memory: hybrid
```
  ——暂存
```
<memory>/
```
  文件（会话文件被git忽略，日志文件会被提交）
- ```
git.memory: commit-all
```
  ——暂存
```
<memory>/
```
  文件
- ```
git.tasks: commit-all
```
  ——暂存
```
.groove/tasks/
```
  文件
- ```
git.hooks: commit-all
```
  ——暂存
```
.groove/hooks/
```
  文件
- 若有文件被暂存：使用
```
YYYY-MM-DD end
```
  作为提交信息提交
- 若无文件可暂存：静默跳过提交
最后一个工作日检测：使用本地日历日期；若在周末运行需优雅处理
所有标准步骤完成后：检查
```
.groove/hooks/end.md
```
是否存在
- 若存在：读取
```
## Actions
```
  部分并按顺序执行每个条目；上报每个条目的完成情况
- 若不存在：静默跳过