template-sync

Synchronize template updates from yellow-seed/template while preserving local customizations.

Updated Sep 20, 2025
One-click install
npx skills add https://github.com/yellow-seed/crypto_wallet_tool --skill template-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: template-sync
Source: https://github.com/yellow-seed/crypto_wallet_tool/tree/main/.github/skills/template-sync
Command: npx skills add https://github.com/yellow-seed/crypto_wallet_tool --skill template-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the synchronization of template updates from yellow-seed/template into your repository while preserving project-specific customizations.

Core Features & Use Cases

  • Non-destructive synchronization: apply only necessary changes without overwriting local overrides.
  • Selective application: tailor updates to target files (CI/CD workflows, documentation, configuration files) and skip project-specific changes.
  • Transparency and control: preview diffs and require user confirmation before applying updates.

Quick Start

Run a sync request to pull the latest template changes and review proposed updates before applying.

Frequently Asked Questions about template-sync

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

FAQPage Schema
How do I synchronize template updates across multiple repositories without losing customizations?

Template synchronization automatically applies updates from a source template to your repositories while preserving project-specific changes. It uses Git diffs to detect what's changed, shows you a preview, and only applies updates after your confirmation, ensuring your local overrides remain intact.

Can I selectively update CI/CD workflows and documentation while skipping other template changes?

Yes, selective synchronization lets you target specific file types—CI/CD workflows, documentation, and configuration files—and skip project-specific modifications. You review proposed changes before applying them, maintaining full control over which updates merge into your repo.

What's the safest way to apply template changes across a repository without manual merge conflicts?

Non-destructive synchronization compares your repository against the template, detects differences via Git, and proposes only necessary changes. GitHub CLI and Git handle the diff detection, you preview the changes, and updates apply only after explicit confirmation to prevent unintended overwrites.

How do I automate keeping multiple repositories in sync with a shared template?

Repository synchronization automation targets multiple repos based on their template source, detects template updates via Git, and coordinates selective application across CI/CD and configuration files. Automation runs controlled syncs with user confirmation at each step, ensuring consistency without breaking project-specific customizations.

Does this work with GitHub repositories and standard Git workflows?

Template synchronization relies on Git and GitHub CLI to detect diffs and manage updates, making it compatible with GitHub-hosted repositories and standard Git workflows. It integrates into your existing CI/CD pipelines and respects your version control structure.