sovereign-sync

Review and apply upstream framework updates to a local Sovereign Ecosystem vault.

2|Updated Mar 9, 2026

Search Tags:#automation #git #workflow #review #sync #upstream

Ready to run

npx skills add https://github.com/infinitegameplayer/sovereign-ecosystem --skill sovereign-sync

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sovereign-sync
Source: https://github.com/infinitegameplayer/sovereign-ecosystem/tree/main/Council%20Chamber/Skills/Sovereign%20Sync
Command: npx skills add https://github.com/infinitegameplayer/sovereign-ecosystem --skill sovereign-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill helps maintain alignment between your local Sovereign Ecosystem vault and the upstream repository, reducing drift and manual review effort.

Core Features & Use Cases

Classifies upstream changes into FRAMEWORK, SEEDED, and USER changes for clear decision points.
Reads diffs, prompts for per-file review, and guides safe application of approved updates.
Supports monthly or on-demand sync to keep your environment current while preserving personalization.

Quick Start

Run the Sovereign Sync workflow to compare your vault against upstream and review changes.

Frequently Asked Questions about sovereign-sync

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

FAQPage Schema

How do I sync a local git repository with upstream changes without overwriting my customizations?▼

To sync a local git repository without losing customizations, the workflow diffs files against HEAD and categorizes changes as FRAMEWORK, SEEDED, or USER. This classification allows you to selectively review and apply upstream updates while preserving your personalized vault configurations.

What is the best way to review upstream framework updates before applying them?▼

The best way to review upstream framework updates is to run a diff check that categorizes changes into FRAMEWORK, SEEDED, and USER groups. This prompts per-file review, ensuring you only apply approved updates to your local repository.

How does categorizing git diffs as FRAMEWORK, SEEDED, or USER help with repository sync?▼

Categorizing git diffs as FRAMEWORK, SEEDED, or USER helps repository sync by creating clear decision points for each file. It separates core upstream updates from seeded templates and personal user changes, guiding safe and selective application.

Do I need a configured upstream remote to review and apply selective git updates?▼

Yes, you need a configured upstream remote and a local vault path to review and apply selective git updates. The workflow requires this remote to fetch changes and run the node-based scripts that perform the check, diff, and apply operations.

Can I use node-based scripts to automate a monthly git workflow sync?▼

Yes, you can use node-based scripts to automate a monthly git workflow sync. The scripts perform check, diff, and apply operations on demand, allowing you to compare your local vault against the upstream remote and apply categorized updates safely.

What happens to my SEEDED and USER files when I apply upstream framework updates?▼

When applying upstream framework updates, your SEEDED and USER files are protected through the categorization process. The workflow reads the diffs, identifies these personalized changes, and prompts you for per-file review so you can skip or selectively apply updates.