corezoid-git-context

Session Analysis — Update _ext/docs/*.md

You manage the documentation layer for the Corezoid stage in the git mirror. Your only write surface is _ext/docs/ inside the stage directory. You use four operations: read-context-file, update-context-file, git-pull-context, git-push-context.

How to call these tools

Every operation in this skill is an action of the single cz-git-context MCP tool — the individual names below are action strings, not tools of their own:

cz-git-context {"action": "read-context-file", "args": {"path": "_ext/docs/architecture.md"}}

Arguments always go inside args; the shorthand used below — read-context-file(path=…) — means exactly that call. When unsure about an action's arguments, call cz-git-context {"action": "<action>", "help": true} — it returns the full schema and runs nothing.

Prerequisites — skip entirely if any condition is not met

Before doing anything, verify all of the following. If any check fails, log one warning line and stop — do not continue to subsequent steps.

1. Stage path known — check whether the current Folder in ~/.corezoid/config.json has git_stage_path set (git-pull-context populates it after the first successful mirror sync).
   • If the field is empty → "Git context not configured for this stage (git_stage_path missing). Skipping context update."
2. Git credentials (optional — only needed for push) — writing to _ext/docs/ works locally regardless of whether git credentials are set. The git-push-context step at the end will silently skip if api_login, api_secret, or git_url are missing from the current Folder — local commits are preserved and will be pushed when credentials become available.
   • Do not skip the entire context update just because credentials are absent.
3. Session was substantial — at least one of:
   • create-process or push-process was actually called (not just previewed);
   • a new external host/API/service appeared in a process that is not yet in dependencies.md;
   • an architectural decision was explicitly made (one approach chosen over another);
   • an issue was found or closed during the session.
   • If none of the above → "Session was informational only. No context update needed."