memory-ci-capture

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Memory CI Capture

Memory CI 捕获

Turn a meaningful GitHub delivery moment into project memory. GitHub records the mechanics. Basic Memory remembers what changed and why.

将有意义的GitHub交付时刻转化为项目记忆。GitHub记录操作机制，Basic Memory则记住变更内容及其原因。

Inputs

输入

Read the

ProjectUpdateContext

JSON produced by

bm ci collect

.github/basic-memory/project-update-context.json

. Treat it as the immutable source of truth for repository, event type, PR number, workflow run, SHA, source URL, timestamps, and deployment environment.

Do not invent tests, deploy checks, linked issues, product impact, or decisions. If evidence is absent, say so briefly in

verification

or leave the field empty.

读取由

bm ci collect

生成的

ProjectUpdateContext

JSON文件，路径为

.github/basic-memory/project-update-context.json

。将其视为仓库、事件类型、PR编号、工作流运行、SHA、源URL、时间戳和部署环境的不可变事实来源。

请勿虚构测试、部署检查、关联问题、产品影响或决策内容。如果相关证据缺失，在

verification

字段中简要说明或留空。

Output

输出

Return only JSON matching the

AgentSynthesis

shape:

json

{
  "summary": "What changed.",
  "why_it_matters": "Why this update matters for future humans and agents.",
  "user_facing_changes": [],
  "internal_changes": [],
  "verification": [],
  "follow_ups": [],
  "decision_candidates": [],
  "task_candidates": []
}

仅返回符合

AgentSynthesis

结构的JSON：

json

{
  "summary": "变更内容。",
  "why_it_matters": "此更新对未来人员及Agent的重要性。",
  "user_facing_changes": [],
  "internal_changes": [],
  "verification": [],
  "follow_ups": [],
  "decision_candidates": [],
  "task_candidates": []
}

Synthesis Rules

合成规则

Prefer a short explanation over a commit-by-commit changelog.
Preserve intent, changed behavior, source links, verification evidence present in the context, and concrete follow-ups.
Put explicit product or architecture decisions in
```
decision_candidates
```
only when the source context clearly contains them.
Put future work in
```
task_candidates
```
only when it is concrete enough to act on.
Keep the tone factual and useful. This is project memory, not marketing copy.

优先使用简短说明，而非逐提交的变更日志。
保留上下文里的意图、变更行为、源链接、验证证据，以及具体的后续事项。
仅当源上下文明确包含明确的产品或架构决策时，才将其放入
```
decision_candidates
```
中。
仅当未来工作足够具体可执行时，才将其放入
```
task_candidates
```
中。
保持语气客观实用。这是项目记忆，而非营销文案。

Event Guidance

事件指引

For merged pull requests, focus on why the PR existed, what area changed, what issues it advanced or closed, and what verification evidence appears in the context.

For production deploys, focus on what reached production, the deployed SHA, environment, workflow run, and verification evidence. Do not overclaim success beyond the workflow and source facts.

对于已合并的拉取请求，重点关注PR存在的原因、变更的领域、推进或关闭的问题，以及上下文中呈现的验证证据。

对于生产环境部署，重点关注已上线的内容、部署的SHA、环境、工作流运行情况及验证证据。请勿超出工作流和源事实过度宣称成功。