memory-commit

Promotes working notes into durable Atmina wiki pages with typed evidence and read-back verification.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/latentminds-ai/atmina-plugins --skill memory-commit-latentminds-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-commit
Source: https://github.com/latentminds-ai/atmina-plugins/tree/main/plugins/atmina-codex/.agents/skills/memory-commit
Command: npx skills add https://github.com/latentminds-ai/atmina-plugins --skill memory-commit-latentminds-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Decisions, facts, and procedures captured during a coding session often vanish or are written as unverifiable prose. This Skill commits durable memory into an Atmina Knowledge Base with typed, pinned evidence and proves the record survived by reading it back, since malformed records are dropped silently on read. ## Core Features & Use Cases - Typed evidence promotion: Writes durable pages into wiki/decisions, wiki/procedures, wiki/facts, wiki/preferences, wiki/relationships, or wiki/open-questions with schema 1 frontmatter, provenance fields, and at least one typed evidence entry. - Pinning recipe: Pins in-KB claims to an exact file version and line span using file_history, versioned read_file, and a span_sha256 hash, while external sources get an https URL and retrieval date and unlocatable claims are marked unattested. - Read-back self-check: Re-parses the written page against a 35-item checklist and compares the product's attestation verdict, stopping with a structured report when the write did not survive. - Use Case: After a user corrects the agent's approach and a decision is settled with a stated reason, commit it as a durable decision page whose claims cite pinned spans of the source wiki pages, then verify each entry reads back as attested. ## Quick Start Use the memory-commit skill to commit this decision with typed evidence and prove the write survived.

Frequently Asked Questions about memory-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I commit a durable decision to an Atmina Knowledge Base?

Write a page under wiki/decisions/ using write_file with schema 1 frontmatter, source, observed, and status fields, plus at least one typed evidence entry. Then read the page back and re-parse it to confirm the record survived, since Atmina performs no write-time validation.

How do I pin an evidence entry to a specific file version and line span?

Call file_history to get head_version, then read_file at that version to obtain the exact bytes. Count stored lines from the opening frontmatter delimiter, hash the joined span with SHA-256, and write pinned_version plus span_sha256 on the entry with a body link after the marker.

When should a claim be marked unattested instead of confirmed?

Mark a claim unattested when you cannot locate any artefact supporting it. It must live as an Open Question with status unresolved in wiki/open-questions/, carry no locator field, and its note must begin with UNATTESTED — never write it as a confirmed Fact or Procedure.

Why did my evidence entry disappear after writing the page?

Entries are dropped silently for malformed ids, duplicate keys, missing type or note fields, CRLF line endings, or a schema value other than the integer 1. The read-back self-check re-parses the returned bytes against the checklist to identify exactly which item failed.

Can a chronicle path be used as a wiki-page evidence locator?

No. A wiki-page entry resolves its path under wiki/, so a chronicle path comes back unresolved. Chronicle paths belong only in the source field as prose provenance; typed evidence must use a resolvable wiki path or an external URL.