LOCALIZATION / GitHub community
VS Code Extension Localization
Localizes VS Code extensions by routing each string to its correct target: package manifest files, walkthrough markdown, or code l10n bundles.
“Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practices”
01 / THE REASONING
Why this made the selection.
- Three localization approaches keyed to resource type (manifest, walkthrough, code strings) instead of one blanket rule applied to all strings.
- File conventions are concrete and checkable: package.nls language files, per-language walkthrough markdown, and bundle.l10n language bundles.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- skills/vscode-ext-localization/SKILL.md
- LICENSE
- SKILL.md and LICENSE re-read at 3a685010 on 2026-10-13 for the downloadable definition; both byte-identical at HEAD 156736fb (git blob SHAs).
- vercel-labs/skills@7407f3893ad4dceab546ac002c3ef806e4000c73:README.md
Our findings
- The skill separates contributed-configuration strings, walkthrough content and code messages into three distinct localization paths.
- Each path names its artifact pattern in the VS Code convention rather than inventing project-local filenames.
- The whole definition is 25 lines with no helpers or references, which bounds what it can get wrong but also what it covers.
- The definition distinguishes package contribution strings, walkthrough Markdown and source-code messages, assigning each a different locale-file pattern and requiring updates for every currently available language.
Not established by this review
- No extension was localized with this skill.
- Artifact patterns were read, not validated against the VS Code localization documentation.
- Not executed: it was not installed or run.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Add a skill to your workflow.
DOCUMENTED COMMAND
npx skills add github/awesome-copilot/skills/vscode-ext-localization --skill vscode-ext-localizationRun in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.
Optional: install the reviewed revision
Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose.
npx skills add https://github.com/github/awesome-copilot/tree/3a685010a7afdc0dbd4c83b7fbda6c316aa516e5/skills/vscode-ext-localization --skill vscode-ext-localization- Install the complete skill directory; select your AI tools and project or global scope.
- Review the instructions before invoking them. The source revision shown here is the one reviewed; the installer was not executed or version-pinned by this review.
- For manual installation instead, download the complete bundle from https://undominated.ai/resources/skills/github-vscode-ext-localization/bundle.zip and extract it into a new directory. It holds SKILL.md unchanged at revision 3a685010, the upstream licence and an attribution file.
- Place the extracted directory in your host's documented skills directory, named vscode-ext-localization. Keep SKILL.md and the licence together.
Before you start
- Node.js/npm and git for the documented Skills installer
- An agent host that supports the skill format
- A VS Code extension checkout with permission to add locale files
THE COMPLETE REVIEWED DEFINITION
Read it before you reuse it.
Original source bytes, with attribution.
Review the host-specific setup notes above.
---
name: vscode-ext-localization
description: 'Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practices'
---
# VS Code extension localization
This skill helps you localize every aspect of VS Code extensions
## When to use this skill
Use this skill when you need to:
- Localize new or existing contributed configurations (settings), commands, menus, views or walkthroughs
- Localize new or existing messages or other string resources contained in extension source code that are displayed to the end user
# Instructions
VS Code localization is composed by three different approaches, depending on the resource that is being localized. When a new localizable resource is created or updated, the corresponding localization for all currently available languages must be created/updated.
1. Configurations like Settings, Commands, Menus, Views, ViewsWelcome, Walkthrough Titles and Descriptions, defined in `package.json`
-> An exclusive `package.nls.LANGID.json` file, like `package.nls.pt-br.json` of Brazilian Portuguese (`pt-br`) localization
2. Walkthrough content (defined in its own `Markdown` files)
-> An exclusive `Markdown` file like `walkthrough/someStep.pt-br.md` for Brazilian Portuguese localization
3. Messages and string located in extension source code (JavaScript or TypeScript files)
-> An exclusive `bundle.l10n.pt-br.json` for Brazilian Portuguese localization
The download contains SKILL.md. Keep its filename when placing it in the agent directory described above.
By GitHub community. Exact upstream source ↗ · Licence · Attribution
SHA-256 a238b58545bc23476ac0bd6451e9b01a225cb125096b90b3425e8e08943e3d6c
Read the applicable licence
MIT License Copyright GitHub, Inc. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://github.com/github/awesome-copilot/blob/3a685010a7afdc0dbd4c83b7fbda6c316aa516e5/skills/vscode-ext-localization/SKILL.md
Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, compatibility, access
https://github.com/github/awesome-copilot/blob/3a685010a7afdc0dbd4c83b7fbda6c316aa516e5/LICENSE
Supports: license
https://github.com/github/awesome-copilot/blob/3a685010a7afdc0dbd4c83b7fbda6c316aa516e5/README.md
Supports: install, compatibility, access
https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/README.md
Supports: install
https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/src/git.ts
Supports: install
https://raw.githubusercontent.com/github/awesome-copilot/3a685010a7afdc0dbd4c83b7fbda6c316aa516e5/skills/vscode-ext-localization/SKILL.md
Supports: review.findings, bestFor