Skill

canvas-sync

Synchronizes Claude canvas state across team sessions via git pull and commit. Ensures shared product knowledge before/after discussions or conflict resolution.

Git

git-workflow

npx claudepluginhub haabe/mycelium --plugin mycelium

Tool Access

This skill uses the workspace's default tool permissions.

Preview

- Starting a new session (pull latest canvas)

SKILL.md

Similar Skills

canvas-update

Updates project canvas YAML files like purpose.yml, north-star.yml, and opportunities.yml with new evidence, ensures cross-file consistency, logs changes, and runs counter-argument checks.

mycelium

shiplog

Orchestrates GitHub issues/PRs/branches as knowledge graph for traceability in planning, brainstorming, designs, architectural decisions, session resumption. /shiplog.

19 files

shiplog

autology-workflow

Orchestrates knowledge workflow after commits, pushes, PRs, or decisions: triages context, syncs existing docs, captures new items with topology hints to keep docs accurate.

4 files

autology

Stats

Parent Repo Stars24

Parent Repo Forks4

Last CommitMay 9, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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 /mycelium: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.