sync-provider

Synchronize external provider repository changes into a local project while preserving customizations.

567|82|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/pedronauck/skills --skill sync-provider
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-provider
Source: https://github.com/pedronauck/skills/tree/main/skills/sync-provider
Command: npx skills add https://github.com/pedronauck/skills --skill sync-provider

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tsx, pnpm, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of synchronizing changes from external provider repositories into your local project while ensuring that your custom modifications are safely preserved.

Core Features & Use Cases

  • Automated Syncing: Checks for new commits, generates diffs, and applies changes from cloned repositories.
  • Customization Preservation: Intelligently merges upstream changes with local customizations, preventing data loss.
  • Use Case: When an external AI provider (like Gemini or Claude) releases an update, this Skill helps you integrate those changes into your local version without overwriting your unique configurations or additions.

Quick Start

Use the sync-provider skill to sync the claude-code provider.

Frequently Asked Questions about sync-provider

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

FAQPage Schema
How do I sync upstream changes from an external provider repository without overwriting local customizations?

To sync upstream changes, this Skill automates checking for new commits via GitHub CLI, generating detailed diffs, and incrementally applying changes to your local project while intelligently preserving your existing custom modifications.

What is the best way to merge updates from cloned AI provider repositories into my local project?

Merging updates from cloned AI provider repositories is handled by performing deep analysis on generated diffs, planning refactors, and applying changes incrementally to ensure your unique local configurations are not lost during the synchronization.

Do I need GitHub CLI and pnpm installed to synchronize external provider updates?

Yes, you need GitHub CLI to check for new upstream commits and pnpm along with tsx as dependencies to execute the scripts required for synchronizing external provider updates into your local environment.

Does the sync-provider Skill work with locally created providers like opencode?

No, it specifically excludes locally created providers like opencode, focusing exclusively on synchronizing updates from cloned external provider repositories such as Gemini or Claude into your local project.

Can I automate the workflow of checking for new commits and generating diffs for external providers?

Yes, you can automate this workflow as the Skill checks for new commits, generates detailed diffs, performs deep analysis, and plans refactors before incrementally applying the upstream changes.

What are the limitations when preserving local customizations during a git sync?

While it intelligently merges upstream changes to prevent data loss, limitations arise if custom modifications heavily conflict with upstream refactor plans, requiring manual intervention to resolve complex overlaps during synchronization.