mcpField
M
memory-ci-capture

memory-ci-capture

github.com/basicmachines-coDevelopment4.4k1.0k installsUpdated today
Repository

About memory-ci-capture

memory-ci-capture is a skill that turns GitHub delivery context into concise, structured project memory. It uses the JSON collected by `bm ci collect` and limits its synthesis to evidence in that context.

Key features

  1. 01Read `ProjectUpdateContext` JSON
  2. 02Summarize merged pull requests
  3. 03Capture production deployment details
  4. 04Preserve source links and verification evidence
  5. 05Avoid unsupported claims and decisions

Use cases

  1. 01Record why a merged PR matters
  2. 02Document changes delivered to production
  3. 03Create factual follow-ups from CI context

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/basicmachines-co/basic-memory --skill memory-ci-capture

After installing, type/memory-ci-capturein Claude Code to confirm it loaded.

Details

From the project README

Memory CI Capture

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

Inputs

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.

Output

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": []
}

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.

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.

Comments

Markdown supported