add-policy

Add and review VS Code enterprise configuration policies for core and extension settings.

Updated Aug 27, 2026

Search Tags:#vscode #configuration #policy #export #copilot #managed settings

Ready to run

npx skills add https://github.com/THRISHAL12345/Project_X --skill add-policy-thrishal12345

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: add-policy
Source: https://github.com/THRISHAL12345/Project_X/tree/main/apps/vscode-fork/.github/skills/add-policy
Command: npx skills add https://github.com/THRISHAL12345/Project_X --skill add-policy-thrishal12345

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you add, review, and maintain VS Code configuration policies without breaking enterprise policy export, localization, or runtime behavior.

Core Features & Use Cases

Policy Registration: Add or modify a configuration property that uses a policy definition and keep the metadata aligned with VS Code conventions.
Managed Settings Wiring: Declare managed-settings keys, route them through the canonical policy bag, and handle preview-feature gating when required.
Policy References: Reuse one enterprise policy across multiple settings with policyReference while preserving type consistency and export correctness.
Operational Example: Use this Skill when updating a chat or Copilot setting that must be locked by organization policy and verified through export and test workflows.

Quick Start

Ask for help adding or reviewing a VS Code policy, including the required policy metadata, managed-settings mapping, and export/test steps.

Frequently Asked Questions about add-policy

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

FAQPage Schema

How do I add a new enterprise configuration policy in VS Code?▼

To add an enterprise configuration policy in VS Code, you register a configuration property with correct policy metadata, declare managed-settings keys, and ensure type alignment and localization for export compatibility.

When do I need to use managed settings and policy definitions in VS Code?▼

You need managed settings and policy definitions in VS Code when a configuration property must be locked by organization policy, requiring canonical policy bag routing and preview-feature gating for enterprise enforcement.

Can I reuse one enterprise policy across multiple VS Code settings?▼

Yes, you can reuse one enterprise policy across multiple VS Code settings using policyReference, which preserves type consistency and ensures policy-data export correctness across the codebase.

How do I wire Copilot or chat settings to be locked by organization policy?▼

To lock Copilot or chat settings by organization policy, you declare managed-settings keys, route them through the canonical policy bag, apply preview-feature gating, and verify through export and test workflows.

Why is my VS Code configuration policy breaking enterprise policy export?▼

VS Code configuration policy export breaks when policy metadata, managed-settings key definitions, localization, or type alignment are incorrect, requiring validation against policy-data export compatibility scenarios.

Does VS Code policy registration require localization and type alignment?▼

Yes, VS Code policy registration requires correct localization and type alignment to maintain enterprise policy export compatibility and ensure runtime behavior matches managed-settings wiring conventions.