memory-worktree

Solid

Verify, customize, or opt out of moflo's AUTOMATIC durable-learning sharing across git worktrees / Conductor workspaces on one machine. As of the worktree-auto-sharing change this is on by default — learnings converge across a repo's worktrees with no setup. Use when the user asks "is memory shared across my worktrees?", "where are my worktree learnings stored?", "turn off worktree memory sharing", "share learnings across my separate clones", or "point my worktrees at a custom store". For a team or cross-machine (git-tracked) sharing, use /memory-team instead.

AI & Automation 18 stars 1 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
43
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# /memory-worktree — Durable Sharing Across Worktrees (Automatic) Working across git worktrees is a core moflo competency, so durable-learning sharing across the worktrees of a repo is now **automatic and on by default**. When a checkout is part of a repo with worktrees in play, moflo derives a shared durable store at **`<git-common-dir>/moflo/durable.db`** and converges the `learnings` + `knowledge` namespaces across every worktree at session start — no config. A plain single checkout writes nothing and behaves exactly as before. This skill is for the three things you might still want: **verify** it's working, **customize** where it stores (or extend it to non-worktree clones), or **opt out**. > Only the durable slice travels. Structural + ephemeral data stays local per checkout and rebuilds > itself — the same safety model the auto path is built on (a dedicated `durable.db`, never a full > `moflo.db`). See [[memory-team]] for the git-tracked, cross-machine variant. **Arguments:** `$ARGUMENTS` — `--off` to opt out, `--path <store>` to set a custom shared store. ## When to use - "Is memory / are learnings shared across my worktrees?" → **verify** (Step 1). - "Where are my worktree learnings stored?" → it's `<git-common-dir>/moflo/durable.db`; verify to confirm. - "Turn off / disable worktree memory sharing" → **opt out** (Step 2). - "Share learnings across my separate clones / a custom location" → **customize** (Step 3). For a team, or your own laptop+desktop over git,...

Details

Author
eric-cielo
Repository
eric-cielo/moflo
Created
6 months ago
Last Updated
2 days ago
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

memory-team

Guided setup for sharing moflo's durable learnings through a git-tracked JSONL artifact — for a whole TEAM on one repo, OR for one person across several MACHINES (a team of one). Use when the user says "share learnings with my team", "commit our moflo memory", "sync memory across my laptop and desktop", "set up memory.team_artifact", or "auto-export learnings on every PR". Installs a pre-commit hook so the artifact rides along in every commit. For many worktrees on ONE machine, use /memory-worktree instead.

18 Updated 2 days ago
eric-cielo
Code & Development Listed

team-project-memory

Route shared project-memory work to the smallest specialized skill. Use when configuring, using, reviewing, or improving reusable knowledge shared across developers, agents, sessions, or machines.

0 Updated 1 months ago
meharajM
AI & Automation Listed

memory-write

Captures a durable fact to project memory through the kit's safe write path (Poison_Guard secret/injection screening + home-path sanitization + dedup + conflict detection) — preferring the cmk MCP tools (mk_remember / mk_forget / mk_trust) when connected, falling back to the cmk CLI. Use when the user says "remember this", "note this", "save this", "from now on", "going forward", "I prefer", "I don't like", "we decided", "we agreed", or otherwise states a durable preference, decision, or environment fact worth carrying across sessions. Also covers correcting a saved fact ("update memory: X is now Y"), removing one ("forget about X"), and adjusting how much a saved fact is trusted ("trust this", "that's important — keep it", "that's not important / I'm not sure about that / low priority"). Skip throwaway chatter and facts that only matter to the current task.

6 Updated today
LH8PPL