菜单
Synthesize GitHub delivery context into a concise Basic Memory project update. Use in CI after `bm ci collect` prepares a ProjectUpdateContext; return only structured AgentSynthesis JSON for `bm ci publish`.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Orient Claude from Basic Memory before substantial repo work by reading active tasks, open decisions, recent checkpoints, and repo conventions. Use when resuming old work or when the user asks where things stand.
Set up the Basic Memory plugin for this project — a short guided interview that configures the project mapping, seeds note schemas, learns or suggests placement conventions, and enables capture reflexes. Use when the user runs /basic-memory:bm-setup, says "set up basic memory", or asks to configure/bootstrap the plugin.
Show the Basic Memory plugin's current state for this project — active project, capture folders, output style, recent session checkpoints, and whether Basic Memory is reachable.
Save a deliberate Codex work checkpoint to Basic Memory with changed files, verification, decisions, blockers, and the next action.
Orient Codex from Basic Memory before substantial repo work by reading active tasks, decisions, recent Codex checkpoints, and repo conventions.
Set up Basic Memory for Codex at user or project level by mapping a Basic Memory project and seeding schemas.
| name | memory-ci-capture |
| description | Synthesize GitHub delivery context into a concise Basic Memory project update. Use in CI after `bm ci collect` prepares a ProjectUpdateContext; return only structured AgentSynthesis JSON for `bm ci publish`. |
Turn a meaningful GitHub delivery moment into project memory. GitHub records the mechanics. Basic Memory remembers what changed and why.
Read the ProjectUpdateContext JSON produced by bm ci collect at
.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.
Return only JSON matching the AgentSynthesis shape:
{
"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": []
}
decision_candidates only
when the source context clearly contains them.task_candidates only when it is concrete enough to act on.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.