vscode-ext-localization▌
github/awesome-copilot · updated Apr 8, 2026
Localize VS Code extensions across configurations, walkthrough content, and source code messages.
- ›Three localization approaches: package.nls.LANGID.json for settings, commands, menus, and views; markdown files for walkthrough content; bundle.l10n.LANGID.json for source code strings
- ›Covers all user-facing resources including contributed configurations, commands, menus, views, ViewsWelcome, and walkthrough titles and descriptions
- ›Requires creating or updating localization files for all
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.
- Configurations like Settings, Commands, Menus, Views, ViewsWelcome, Walkthrough Titles and Descriptions, defined in
package.json-> An exclusivepackage.nls.LANGID.jsonfile, likepackage.nls.pt-br.jsonof Brazilian Portuguese (pt-br) localization - Walkthrough content (defined in its own
Markdownfiles) -> An exclusiveMarkdownfile likewalkthrough/someStep.pt-br.mdfor Brazilian Portuguese localization - Messages and string located in extension source code (JavaScript or TypeScript files)
-> An exclusive
bundle.l10n.pt-br.jsonfor Brazilian Portuguese localization
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★45 reviews- ★★★★★Sakura Mehta· Dec 16, 2024
Useful defaults in vscode-ext-localization — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Ishan Bhatia· Dec 12, 2024
I recommend vscode-ext-localization for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Isabella Mensah· Dec 8, 2024
vscode-ext-localization has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Henry Menon· Dec 8, 2024
Keeps context tight: vscode-ext-localization is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Isabella Johnson· Dec 4, 2024
Registry listing for vscode-ext-localization matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Mia Johnson· Nov 27, 2024
vscode-ext-localization is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Isabella Garcia· Nov 23, 2024
vscode-ext-localization reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Evelyn Farah· Nov 7, 2024
We added vscode-ext-localization from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Yuki Okafor· Nov 3, 2024
Solid pick for teams standardizing on skills: vscode-ext-localization is focused, and the summary matches what you get after install.
- ★★★★★Omar Chawla· Oct 26, 2024
vscode-ext-localization reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 45