merge-copilot-settings

Merge settings.base.json top-level keys into local VS Code settings.json.

1|Updated Apr 14, 2026

Search Tags:#config #merge #settings #copilot #settings.json #vs-code #machines

Ready to run

npx skills add https://github.com/bhanford9/vs-code-copilot-tools --skill merge-copilot-settings

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: merge-copilot-settings
Source: https://github.com/bhanford9/vs-code-copilot-tools/tree/main/skills/merge-copilot-settings
Command: npx skills add https://github.com/bhanford9/vs-code-copilot-tools --skill merge-copilot-settings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merge local VS Code settings with the shared Copilot base to synchronize configurations.

Core Features & Use Cases

Merge settings.base.json into local settings.json, overwriting top-level keys while preserving machine-specific keys.
Apply base Copilot configuration after git pull, on new machine setup, or when asked to merge or apply base settings.
Verify merged settings by checking critical keys like chat.* paths and ensuring required keys exist.

Quick Start

Run the merge-copilot-settings skill to apply the base Copilot settings to your local VS Code settings.

Frequently Asked Questions about merge-copilot-settings

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

FAQPage Schema

How do I synchronize VS Code Copilot settings across multiple machines?▼

To synchronize Copilot settings across machines, you can merge a shared settings.base.json file into your local VS Code settings.json, applying shared base configurations while preserving machine-specific keys.

How do I apply base Copilot configurations to a new VS Code setup?▼

Applying base Copilot configurations involves merging top-level keys from a repository's settings.base.json into your local settings.json, which is triggered during machine provisioning or after pulling repository updates.

What is the best way to merge shared VS Code settings without losing local configurations?▼

Merging shared VS Code settings without losing local configurations works by overwriting top-level keys from settings.base.json into settings.json while deliberately preserving machine-specific keys.

Does merging Copilot settings overwrite my machine-specific VS Code keys?▼

Merging Copilot settings overwrites top-level keys from the base configuration but explicitly preserves machine-specific keys in your local settings.json to maintain your local environment setup.

How can I verify that my merged Copilot settings applied correctly?▼

Verifying merged Copilot settings involves checking critical keys like chat.* paths and ensuring required configuration keys exist within the local settings.json file after the merge process completes.

When should I trigger a Copilot settings merge in VS Code?▼

Trigger a Copilot settings merge when provisioning a new machine, after completing a git pull of your configuration repository, or when explicitly instructed to apply base settings.