Stats
Actions
Tags
From mycelium
Synchronizes Claude canvas state across team sessions via git pull and commit. Ensures shared product knowledge before/after discussions or conflict resolution.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mycelium:canvas-syncThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Starting a new session (pull latest canvas)
git pull origin main
Then run /mycelium:diamond-assess to see what changed.
git add .claude/canvas/ .claude/harness/decision-log.md .claude/memory/
git commit -m "canvas: [brief description of what changed and why]"
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.
npx claudepluginhub haabe/mycelium --plugin myceliumUpdates 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.
Generates a visual code review on a Miro board from a PR/MR, local changes, or branch comparison. Produces file-changes tables, architecture/security docs, and diagrams, then links them back to the PR/MR.
Guides git shipping workflow: verifies repo state, creates branches, stages changes, commits with meaningful messages, pushes, and creates GitHub or Bitbucket PRs via CLI.