OpenSkillIndex← back to search
claude-code

Mycelium canvas-sync

Synchronize canvas state across team sessions via git. Ensures all team members see the same product knowledge.

install
source · Clone the upstream repo
git clone https://github.com/haabe/mycelium
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/haabe/mycelium "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.claude/skills/canvas-sync" ~/.claude/skills/haabe-mycelium-canvas-sync && rm -rf "$T"
manifest: .claude/skills/canvas-sync/SKILL.md
source content

Canvas Sync

When to Use

  • Starting a new session (pull latest canvas)
  • Ending a session (commit canvas changes)
  • After team discussion that changes product direction
  • When canvas conflicts arise from parallel work

Workflow

Pull Latest

git pull origin main

Then run 

/diamond-assess
to see what changed.

Commit Changes

git add .claude/canvas/ .claude/harness/decision-log.md .claude/memory/
git commit -m "canvas: [brief description of what changed and why]"

Conflict Resolution

  • Different canvas files: auto-merges (no conflict)
  • Same file, different sections: usually auto-merges
  • Same field conflicting: person with MORE evidence wins
  • When uncertain: discuss as team, log decision

GitOps Principle

The canvas system IS GitOps for product knowledge — git is the single source of truth, changes are declarative (YAML), and updates flow through version control with review. For infrastructure GitOps (ArgoCD, Flux), see JiT tooling detection for Kubernetes/infrastructure-as-code projects.