sync

Deploy code and brain data to a remote VPS via git push and MCP calls.

10|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/fiftynotai/igris-ai --skill sync-fiftynotai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync
Source: https://github.com/fiftynotai/igris-ai/tree/main/.claude/skills/sync
Command: npx skills add https://github.com/fiftynotai/igris-ai --skill sync-fiftynotai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps a project's repository and the centralized VPS brain in sync, removing the manual steps and guesswork required to push code, update the remote service, and upload brain data and metrics.

Core Features & Use Cases

  • Full and selective sync modes: run a complete sync or choose code-only, data-only, or status checks to suit deployment needs.
  • Safe pre-flight checks and deploy workflow: warns about uncommitted changes, counts unpushed commits, pushes to origin, SSH-deploys the repo, and performs health checks.
  • MCP-backed brain data pushes: drains sync queues, pushes brain rows, and uploads event, agent metrics, and budget files when present for analytics and persistent memory synchronization.
  • Use Case: After finishing a feature branch, run a sync to push commits to origin, trigger the remote update script, verify the brain service health, and upload session metrics to the centralized brain.

Quick Start

Run the sync command by invoking /sync to perform a full code and brain data deployment to the configured VPS and remote brain.

Frequently Asked Questions about sync

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

FAQPage Schema
How do I deploy code and brain data to a VPS automatically?

To deploy code and brain data to a VPS, the sync command pushes git commits to origin, runs remote SSH deploy scripts, verifies health endpoints, and uses MCP tool calls to push brain data. It requires configured SSH access and a remote brain API key.

Can I run a partial deploy and push only code or only data to a remote VPS?

Yes, you can run selective sync modes to push code-only or data-only to a remote VPS. This allows you to independently trigger git pushes and SSH deploy commands or focus exclusively on MCP-based brain data pushes for persistent memory synchronization.

What prerequisites do I need to set up before syncing repository state to a VPS?

Before syncing repository state to a VPS, you need SSH access and VPS configuration, along with a remote brain URL and API key. The process performs git status checks to warn about uncommitted changes before attempting to push code or brain data.

How do MCP-based brain data pushes work during a remote deployment?

MCP-based brain data pushes work by draining sync queues and uploading brain rows, event files, agent metrics, and budget files during deployment. This synchronizes persistent memory and analytics data to the centralized remote VPS brain via configured MCP tool calls.

Does the VPS deploy workflow include health checks after pushing git commits?

Yes, the VPS deploy workflow includes health checks after pushing git commits. Following the git push and remote SSH deploy commands, it verifies the service health endpoint to ensure the remote update script executed successfully and the application is running.

How do I synchronize agent metrics and budget files to a centralized brain?

You synchronize agent metrics and budget files to a centralized brain by running the sync command. It automatically detects these files when present and uses MCP tool calls to drain queues and push the data to the remote VPS brain for analytics synchronization.