---
name: daily-change-list
description: >-
  Writes or appends a daily change log markdown under docs/daily after completing
  repo edits (code, migrations, OpenAPI, i18n, configs, docs). Use when finishing
  any task that modified or added files, before telling the user the work is done.
  Triggers: daily changelog, change list, docs/daily, 每日变动, 变动清单.
---

# Daily change list

After **any** substantive edit or addition in this repo (skip pure Q&A with zero file changes), update the daily log **before** reporting completion to the user.

## Output path

```text
docs/daily/{yyyy}-{mm}-{dd}-change-list.md
```

| Placeholder | Meaning |
|-------------|---------|
| `{yyyy}` | 4-digit year |
| `{mm}` | 2-digit month (`01`–`12`) |
| `{dd}` | 2-digit day of month (`01`–`31`) |

Example: 2026-09-24 → `docs/daily/2026-09-24-change-list.md`.

Create `docs/daily/` if missing. **Same calendar day**: append a new session block; do not overwrite earlier entries.

## How to gather changes

1. `git status` and `git diff` (staged + unstaged) for paths touched this session.
2. Summarize **why** and **what** in plain language (modules, APIs, migrations, behavior).
3. Note verification: `make test` / `make lint` result, or `skipped` only for docs-only with no build surface.

Do not paste full diffs. List important files with one-line descriptions.

## Markdown template

**New file** (first entry of the day):

```markdown
# 每日变动 {yyyy}-{mm}-{dd}

## {HH:MM} — {one-line title}

### 概要

- …

### 变更范围

| 类型 | 说明 |
|------|------|
| 功能 / 修复 / 重构 / 文档 / 配置 | … |

### 主要文件

- `path/to/file` — …

### 验证

- `make test`: pass / fail / skipped (reason)

### 关联

- Issue / PR / 对话上下文（如有）
```

**Append** (file already exists): add another `## {HH:MM} — …` section with the same subsections under the existing `# 每日变动` header.

Use `{HH:MM}` in **UTC+8** unless the user specifies another timezone.

## Quality bar

- Chinese or English is fine; match the user’s language when obvious.
- One session block per agent completion; merge duplicate bullets if the same fix is retried.
- If the user explicitly says not to write the daily log, skip.

## Order with other gates

1. Finish code/docs edits.
2. Run `make test` when required (see `verify-before-done.mdc`).
3. Write or append this daily markdown.
4. Tell the user the task is done (mention the daily file path).