upstream-sync

To safely sync upstream updates, this Skill fetches remote repository diffs, categorizes changes, and requires explicit user approval before applying them. It performs a post-merge verification gate running installs, audits, and tests to ensure framework stability.

Automating daily git upstream syncs safely requires operating on cron schedules to catalog remote repository changes. It summarizes impact in plain English and proposes actions, preventing unintended updates by enforcing explicit approval before any merge occurs.

The post-merge verification gate works by running install, audit, and test workflows after upstream updates are applied. This ensures the local framework remains stable and functional immediately following the remote version-control sync process.

Yes, you can review remote repository diffs before approving version-control updates. The Skill fetches the changes, categorizes them, and explains the impact in plain English, waiting for your explicit approval before applying any modifications to the framework.

No, you do not need to manually trigger cron schedules for upstream repository checks. The Skill operates on automated daily cron schedules for routine scanning, but also supports on-demand inquiries whenever you want to manually check for remote framework updates.

Using an approval workflow for git upstream syncs prevents unintended updates from breaking your environment. It fetches diffs, explains changes, and verifies safety post-merge, ensuring you maintain strict version-control integrity over automated remote framework modifications.