config-github-sync

Synchronize shared GitHub configuration files across repositories via safe file copies.

Updated Mar 21, 2026

Search Tags:#automation #templates #github #config #diff #sync

Ready to run

npx skills add https://github.com/tatsushige-i/shared-claude-code --skill config-github-sync

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: config-github-sync
Source: https://github.com/tatsushige-i/shared-claude-code/tree/main/docs/ja-JP/skills/config-github-sync
Command: npx skills add https://github.com/tatsushige-i/shared-claude-code --skill config-github-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill synchronizes shared GitHub configuration assets (ISSUE_TEMPLATE, PULL_REQUEST_TEMPLATE, and workflows) from a central repository into your project by performing file copies, avoiding the limitations of symlinks in GitHub.

Core Features & Use Cases

Resolve and locate shared assets via symlinks from the central shared repository.
Compare local .github assets against the shared source to identify identical, updated, new, or locally present-only files.
Copy selected updates safely, creating missing directories as needed and validating post-copy diffs.
Initialize and maintain CI template synchronization by inferring project language/framework and offering relevant templates.
Standardize configurable label-related setups when applicable.

Quick Start

Run the config-github-sync skill to copy shared .github templates into your repository based on detected diffs.

Frequently Asked Questions about config-github-sync

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

FAQPage Schema

How do I sync GitHub templates across multiple repositories?▼

You can sync GitHub templates by copying shared assets like ISSUE_TEMPLATE and workflows from a central source repository. The process compares local files against the source, identifies diffs, and applies safe, idempotent copies to update targets.

Why do symlinks not work for sharing GitHub configuration files?▼

Symlinks often fail for sharing GitHub configuration files because GitHub does not resolve them correctly in all contexts. Copying the actual files from a central repository ensures the templates are properly recognized and function as intended.

What is the best way to update CI workflows and pull request templates in my repo?▼

The best way to update CI workflows and pull request templates is to copy them from a central shared repository. This method detects project language, infers relevant templates, and validates post-copy diffs to ensure safe synchronization.

Can I detect language-specific GitHub templates when synchronizing configs?▼

Yes, you can detect language-specific GitHub templates during synchronization. The process infers your project's language or framework and offers relevant CI templates to copy, ensuring the configuration matches your development environment.

Does synchronizing shared GitHub configs overwrite my local files?▼

Synchronizing shared GitHub configs does not blindly overwrite local files. It compares local assets against the shared source to identify identical, updated, or locally present-only files, prompting you for updates and validating safe copies.

How do I initialize and maintain CI template synchronization for a new project?▼

To initialize CI template synchronization for a new project, run a sync process that copies shared .github templates. It creates missing directories as needed, applies relevant diffs, and ensures your repository configuration remains up to date.