settings-precedence Skill
VS Code settings precedence rules and common pitfalls. Essential for any code that reads or writes settings. Covers getConfiguration scope, inspect() vs get(), and multi-workspace handling. Published by microsoft in vscode-python-environments.
Decision snapshot
Is this a fit?
Developers using vscode-python-environments, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is settings-precedence Skill?
VS Code settings precedence rules and common pitfalls. Essential for any code that reads or writes settings. Covers getConfiguration scope, inspect() vs get(), and multi-workspace handling. Published by microsoft in vscode-python-environments. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using vscode-python-environments
Declared skill metadata
- Source file: .github/skills/settings-precedence/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use settings-precedence Skill
- Use it for developers using vscode-python-environments.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode-python-environments
- Skill file: .github/skills/settings-precedence/SKILL.md
What it does
VS Code settings precedence rules and common pitfalls. Essential for any code that reads or writes settings. Covers getConfiguration scope, inspect() vs get(), and multi-workspace handling.
Skill instructions
VS Code Settings Precedence Settings precedence bugs corrupt user configurations. This skill documents the correct patterns. Precedence Order (Highest to Lowest) 1. Workspace folder value - Per-folder in multi-root workspace 2. Workspace value - .vscode/settings.json or .code-workspace 3. User/global value - User settings.json 4. Default value - From extension's package.json (⚠️ may come from other extensions!) Core Rules Rule 1: Always Pass Scope to getConfiguration() typescript // ❌ WRONG: Missing scope const config = vscode.workspace.getConfiguration('python-envs'); const value = config.get('pythonProjects'); // workspaceFolderValue will be UNDEFINED because VS Code doesn't know which folder! // ✅ RIGHT: Pass scope (workspace folder or document URI) const config = vscode.workspace.getConfiguration('python-envs', workspaceFolder); const value = config.get('pythonProjects'); When to pass scope: - Reading per-resource settings (scope: "resource" in package.json) - Any multi-workspace s
Verified compatibility and discovery
Frequently asked questions
What is settings-precedence?
settings-precedence is a open-source AI agent skill with Copy skill directory. VS Code settings precedence rules and common pitfalls. Essential for any code that reads or writes settings. Covers getConfiguration scope, inspect() vs get(), and multi-workspace handling.
Who is settings-precedence best for?
settings-precedence is best for reusing agent instructions, scripts, and references.
How do I install settings-precedence?
Install or run settings-precedence using Copy skill directory. Check settings-precedence for the latest setup command.
Is settings-precedence actively maintained?
settings-precedence may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
