rlaope/oh-my-hermes / skills/omh-memory-sync
omh-memory-sync
Verified[omh] Outdated or wrong Hermes memory entries: English-canonical Hermes memory-review guidance: inspect USER.md and MEMORY.md claims and prepare a native write diff without invoking, applying, or observing a native write; for a new fact use `omh-memory-new`, and for a past decision use omh_memory recall or `omh-decision-recall`. Use when the user says: memory-sync, memory curation, memory review, memory inspect, memory check, memory update, context cleanup, curate memory.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 19.5 KB |
| references/source-recovery.md | markdown | 4.3 KB |
references/source-recovery.md
View on GitHub# Recovering From One Wrong Memory Source
When a source turns out to be poisoned, wrong, or no longer trusted, recovery is not a record-by-record review. It starts with the one question the per-record commands cannot answer -- which records came from it -- and it closes on a recall report over this store, not on an exit code.
## Sequence
1. **Enumerate.** `omh memory sources` lists every source label in the store with its record count and the axes it appears on; `omh memory sources --source <label>` returns that source's records. It is a read: it quarantines, retires, and deletes nothing.
2. **Widen.** `omh memory lineage <record-id>` for each returned record. A record derived from a poisoned one carries the claim forward, and this selector does not follow provenance on its own.
3. **Quarantine.** `omh memory attention <record-id> --tier archive` previews, then add `--apply`: the record leaves default recall and stays stored (reversible; `omh memory recall --include-archived` still finds it). `omh memory retire <record-id> --apply` moves only expired or open records and refuses a live one: `omh memory retire <id>` exits 1 with `skipped: not_expired` and moves nothing (only the untargeted sweep exits 0 when it archives nothing). To archive the revision itself, recall the record in the session and call `omh_memory` with `action="retire"` and `reason: no_longer_true`.
4. **Delete only then.** `omh memory prune <record-id> --revision <n> --apply --confirm-hard-delete-local` hard-deletes the manifest-declared OMH-local target set, but accepts only an expired approved volatile record (`prune_requires_expired_approved_volatile` otherwise). For a live record there is no hard-delete path here: `prune` exits 0 with `applied: false` and that reason, so read `applied`, never the exit code; say so and leave it archived. Irreversible; an explicit second step, never folded into the quarantine.
5. **Prove it.** `omh memory recall "<the claim those records answered>"` over this store, or `omh memory recall-incident --record-id <id>` for one record's stored/eligible/selected stages. A recall report whose `included_records` lacks them is the completion evidence (an archived record still appears in `excluded_records` as `archived_tier`). An exit code is not: an untargeted retire sweep that archived nothing and a refused `prune` both exit 0. Neither is `omh memory recall-suite`, which seeds its own fixture corpus in a temporary store -- it proves the recall engine did not regress while you worked, never that this store's records left recall.
## What the selector matches
Two axes carry a record's origin and one record can carry both: `source`, the admission channel recorded at capture, and `source_ref`, the document, ticket, or URL the memory was taken from. A record is listed under every label it carries, so a record admitted from two sources appears under both, and one whose two axes name the same value reports both axes rather than the first.
`source_class` is not an axis. It is a four-value governance classification and every directly captured record is `omh_local`, so indexing it would produce one label matching most of the store and say nothing about where a record came from.
## What it cannot tell you
A record that recorded no source at all is listed under `indeterminate`, never quietly excluded. This selector cannot call it clean and neither can this report; those records stay yours to judge. An unreadable record file is the same answer for a different reason and is listed beside them.
## Reading an empty result
`selected.outcome` separates the three ways to match nothing, because they are three different answers:
- `empty_store` -- nothing readable in the store.
- `source_never_recorded` -- records exist and none of them recorded a source. The selector can exclude nothing here; the whole store is indeterminate.
- `no_records_for_source` -- sources are recorded and this one is not among them. This is the only outcome that means the source contributed nothing.
## Boundaries
The report is `memory_source_index/v1`: OMH-local prepared context, never execution, review, CI, merge, or Hermes internal-memory evidence. Retire archives and prune deletes only the OMH-local target set each one names; neither proves anything about Hermes' own memory files or an external provider's store.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |