brain-sync

Export local state, push to remote, pull updates, and merge brain changes.

78|18|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/toroleapinc/claude-brain --skill brain-sync-toroleapinc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brain-sync
Source: https://github.com/toroleapinc/claude-brain/tree/main/skills/brain-sync
Command: npx skills add https://github.com/toroleapinc/claude-brain --skill brain-sync-toroleapinc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual brain synchronization across devices to ensure consistent Claude Brain state by exporting local state, pushing to remote, pulling updates, merging, and applying them.

Core Features & Use Cases

  • Manual orchestration of brain synchronization across devices.
  • Exports local state, pushes to remote, pulls updates, merges, and applies.
  • Use Case: When you work on multiple machines and need a deterministic, merged brain state without daily re-teaching Claude.

Quick Start

Push local changes, pull remote updates with auto-merge, and review the results to complete a full brain sync.

Frequently Asked Questions about brain-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync my local state across multiple devices?

To sync local state across multiple devices, you export local changes, push them to a remote brain, pull remote updates, and merge them deterministically. This workflow ensures a consistent state without manual re-teaching.

What is the best way to merge remote updates on different machines?

The best way to merge remote updates on different machines is using an auto-merge workflow that pulls changes, applies deterministic merging, prompts for conflict resolution, and provides a final summary of applied changes.

How does the brain synchronization workflow handle conflicts?

The brain synchronization workflow handles conflicts by enforcing validation steps during the merge process. It applies optional auto-merge first, then issues conflict prompts for unresolved discrepancies before completing the final summary.

When do I need manual brain sync for multi-device setups?

You need manual brain sync for multi-device setups when updates occur on different machines and must be consolidated deterministically. It prevents daily re-teaching by exporting local state and merging it with remote updates.

Can I use auto-merge to consolidate updates from different machines?

Yes, you can use optional auto-merge to consolidate updates from different machines. The workflow pulls remote updates, applies the auto-merge process, and prompts you only if conflicts require manual resolution.

Why does my multi-device workflow require a final summary of changes?

A multi-device workflow requires a final summary of changes to verify that the deterministic merge completed correctly. It enforces validation by listing what was exported, pushed, pulled, and merged across your devices.