Zaxy turns agent work into durable, auditable memory: a hash-chained Eventloom log as the source of truth, an embedded temporal knowledge graph for reasoning (local-first, no sidecar; Neo4j/Postgres optional), cited Memory Checkout for compact context, and MCP tools for model-facing retrieval, capture, and feedback.
Skill Claude CodeCodex
Diagnose and fix red CI on zaxy — fetch the right logs, reproduce locally despite the known local quirks (testdoctor hang, benchmark tables), do coverage-ratchet math correctly, and apply the test-vs-source intent rule. Use when CI is red, a check fails on a PR, "make master green", or coverage ratchet fails.
Skill Claude CodeCodex
Cut a zaxy-memory release end-to-end — version bump (all 3 fields), CHANGELOG, PR, CI watch, rebase-merge, master-CI verify on the exact tip, GitHub Release → PyPI publish, post-verify. Use when the user says "cut a release", "ship X.Y.Z", "release this", or after merged work needs to reach PyPI.
Skill Claude CodeCodex
Diagnose and repair Zaxy memory-store incidents — checkout segfaults/hangs, MCP disconnects, LadybugDB corruption (orphan-WAL and bloat variants), orphaned serve processes, and thin/telemetry-only memory. Use when zaxy checkout crashes or hangs, the MCP server keeps disconnecting, or checkout returns no real facts.