[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BRF7JEYRDQ8EWCGFQP1TC":3,"skill-same:01M69BRF7JEYRDQ8EWCGFQP1TC":86},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M69BRF7JEYRDQ8EWCGFQP1TC","ensure-localization",null,"Inspect, author, repair, and review customer-facing RESW and localization YAML resources. Use shared product terminology, translator context, lock annotations, and six file-based checks; the caller supplies the goal and scope.","microsoft\u002Fintelligent-terminal","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69BR4043X0X0KRBRZVGJP2V",2224,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fensure-localization\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"ensure localization","localization","goal","author","lock","inspect","resources","scope","shared","repair","terminology","review","use","context","annotations","translator","yaml","file","product","customer","2026-11-10 10:12:30",false,"---\nname: ensure-localization\ndescription: 'Inspect, author, repair, and review customer-facing RESW and localization YAML resources. Use shared product terminology, translator context, lock annotations, and six file-based checks; the caller supplies the goal and scope.'\n---\n\n# Ensure Localization\n\nUse this shared procedure for customer-facing localization. The caller supplies\nthe goal, scope, and permitted edits; PR or workflow context is not required.\n\n## Product consistency\n\nKeep terminology consistent within each locale and across RESW and localization\nYAML for the same product. Grammar may vary with context, but established product\nkeywords should not alternate between unrelated translations.\n\n## Language-quality acceptance\n\nFor every scoped customer-facing value in a real non-English locale, the final\ntext must actually be in that locale's target language. Copying the English\nsource or leaving a provisional English fallback is not a repair, even when all\nsix checks pass. English locales, source-authoritative locks, and legitimate\nidentical names or technical terms are allowed exceptions; translate the\nunlocked surrounding words.\n\n## Caller context\n\nThe caller owns repository or PR context, trusted revisions, skip policy,\nautomation allowlists, and safe-output rules. This skill owns only the reusable\nfile-based localization procedure.\n\n## Resources\n\n- File checker: [`.\u002Fscripts\u002Flocalization_checks.ps1`](.\u002Fscripts\u002Flocalization_checks.ps1)\n\n## Supported files\n\nThe skill applies to localization resources regardless of their location. The\nchecker supports `.resw` and flat locale `.yml` files; other YAML structures need\nan appropriate parser, not conversion merely to satisfy this checker.\n\nDiscover source and target files using the caller's context and existing layout.\nIn this repository, `en-US` files and direct resource files are common source\nauthorities; these are conventions, not mandatory checker paths.\n\nDo not edit source-authority files just to make translations pass.\n\n## Source-authoring guidance\n\n- Add translator context when wording is ambiguous or depends on UI usage, such\n  as a noun versus a command. Explain the meaning and placeholder roles; avoid\n  boilerplate comments for obvious strings.\n- Use `{Locked}` when the whole value must remain literal, and\n  `{Locked=\"token\"}` for invariant parts such as product names, protocol names,\n  commands, or paths. Use locale-scoped locks only when the exception genuinely\n  applies to those locales; do not exempt entire pseudo-locales by default.\n- Put guidance in the resource's `\u003Ccomment>` for RESW or its associated YAML\n  comment. Preserve annotations in target files where the format requires them.\n- When source edits are not permitted, report missing or contradictory source\n  guidance instead of silently changing source files or inventing meaning.\n  Mechanical checks preserve declared locks; they cannot decide which\n  annotations a new string needs.\n\n## Six checks\n\n| Check | Required args | Purpose |\n| --- | --- | --- |\n| `Test-ResourceSyntax` | `-File` | Parse supported XML or flat locale YAML shape |\n| `Test-ResourceEncoding` | `-File` (`-OriginalFile` optional) | Enforce UTF-8 and expected BOM behavior |\n| `Test-RequiredKeys` | `-SourceFile -TargetFile` (`-Keys` optional for PowerShell callers; CLI uses `-KeysJson` when scoping) | Missing and stale key parity |\n| `Test-PlaceholderParity` | `-SourceFile -TargetFile` (`-Keys` optional for PowerShell callers; CLI uses `-KeysJson` when scoping) | Placeholder identity and count parity |\n| `Test-LockedContent` | `-SourceFile -TargetFile` (`-Locale` sometimes required, `-Keys` optional for PowerShell callers; CLI uses `-KeysJson` when scoping) | Preserve locked values and tokens |\n| `Test-PseudoLocale` | `-SourceFile -TargetFile -Locale` (`-Keys` optional for PowerShell callers; CLI uses `-KeysJson` when scoping) | Catch English fallback and pseudo-style mistakes |\n\nExample commands:\n\n```powershell\npwsh .github\u002Fskills\u002Fensure-localization\u002Fscripts\u002Flocalization_checks.ps1 -Check Test-ResourceSyntax -File \u003Cfile>\npwsh .github\u002Fskills\u002Fensure-localization\u002Fscripts\u002Flocalization_checks.ps1 -Check Test-ResourceEncoding -File \u003Cfile> [-OriginalFile \u003Coriginal-file>]\npwsh .github\u002Fskills\u002Fensure-localization\u002Fscripts\u002Flocalization_checks.ps1 -Check Test-RequiredKeys -SourceFile \u003Csource-file> -TargetFile \u003Ctarget-file> [-KeysJson '[\"key1\",\"key2\"]']\npwsh .github\u002Fskills\u002Fensure-localization\u002Fscripts\u002Flocalization_checks.ps1 -Check Test-PlaceholderParity -SourceFile \u003Csource-file> -TargetFile \u003Ctarget-file> [-KeysJson '[\"key1\",\"key2\"]']\npwsh .github\u002Fskills\u002Fensure-localization\u002Fscripts\u002Flocalization_checks.ps1 -Check Test-LockedContent -SourceFile \u003Csource-file> -TargetFile \u003Ctarget-file> [-Locale \u003Clocale>] [-KeysJson '[\"key1\",\"key2\"]']\npwsh .github\u002Fskills\u002Fensure-localization\u002Fscripts\u002Flocalization_checks.ps1 -Check Test-PseudoLocale -SourceFile \u003Csource-file> -TargetFile \u003Ctarget-file> -Locale \u003Cpseudo-locale> [-KeysJson '[\"key1\",\"key2\"]']\n```\n\nThe script writes one JSON bundle to stdout and exits with the actual status\nmapping:\n\n- `0` → `PASS`\n- `20` → `FIXABLE`\n- `30` → `BLOCKED`\n- `64` → `INVALID_INPUT`\n\n## Batched checks\n\nFor larger scopes, use one `pwsh` process per batch: dot-source\n`localization_checks.ps1` once and call its public functions directly with\nnative PowerShell arguments. Assess the actual returned statuses and findings;\ndo not fabricate results or generate another checker.\n\nRun initial checks before repairs and rerun the affected checks after repairs.\nFor a read-only review, reuse successful check results instead of repeating the\nsame batch. Inspect summaries and non-PASS findings rather than printing every\nbundle into the model context. No separate aggregate checker-report file is\nrequired.\n\nThe agent owns scope completeness and language judgment. Mechanical checks\nsupport that assessment; they cannot establish that every affected resource\nwas discovered or that a translation is correct.\n\n## Reusable procedure\n\n1. Read the exact original localization patch content against the\n   caller-supplied immutable endpoints before choosing keys or counterpart\n   files. Use:\n   `git diff --no-ext-diff --unified=3 \u003Ccomparison-base> \u003Cimmutable-head> -- \u003Cresource paths>`.\n   Supporting summaries such as `git diff --stat`, `--name-only`,\n   `--name-status`, `--numstat`, `git status`, or a worktree-only\n   `git diff -- \u003Cfile>` are useful for discovery but are not sufficient to\n   derive scoped keys, values, or review coverage. If the diff output is\n   truncated, continue fetching the remaining hunks until you have read the\n   full patch for every relevant resource file. Derive the precise added or\n   updated source keys, values, and surrounding context from that exact patch;\n   do not infer scope from file prefixes, neighboring samples, unchanged source\n   lines, or PR summaries.\n   - Source-authority add or update: expand to every shipped localized\n     counterpart that should carry the affected file or keys, even when those\n     target files are unchanged in the git diff.\n   - Target-only edit: inspect that localized target against its source\n     authority.\n   - Source key or file removal: inspect obsolete shipped counterparts with\n     ordinary git and file review. Handle removal or cleanup explicitly instead\n     of claiming `PASS` because no file-pair check ran.\n2. Map each localized target to its source-authority file. In this repository,\n   `.resw` targets map to `...\u002FResources\u002Fen-US\u002F*.resw` or direct\n   `...\u002FResources\u002F*.resw`, and WTA locale targets map to\n   `tools\u002Fwta\u002Flocales\u002Fen-US.yml`.\n3. Before translating changed terms, inspect existing translations in the same\n   locale across both `.resw` files and `tools\u002Fwta\u002Flocales\u002F*.yml`. Reuse\n   established product terminology when the meaning and UI context match. If no\n   repository precedent exists, prefer Microsoft localized terms and flag\n   conflicting existing translations instead of inventing synonyms or rewriting\n   unrelated strings.\n4. Use `-Keys` only for native PowerShell function calls, or `-KeysJson` when\n   invoking the checker script from the CLI. Optional key scoping exists to\n   avoid fixing unrelated old debt, not to hide source additions that the\n   procedure already put in scope. Omit the scope parameter entirely for a\n   whole-file check.\n5. Run `Test-ResourceSyntax` and `Test-ResourceEncoding` on every file you\n   actually inspect.\n6. For each localized target, run `Test-RequiredKeys` against the full scoped\n   source-present change list, then run `Test-PlaceholderParity`,\n   `Test-LockedContent`, and, for pseudo-locales, `Test-PseudoLocale` only for\n   keys that are present in both the source-authority file and that target.\n   If a scoped key is missing on either side, keep the `Test-RequiredKeys`\n   finding and do not force the dependent checks across that absent entry. If\n   the source key or file was removed, handle that cleanup with step 1's\n   explicit review instead of treating the deleted source name as a scoped\n   `-Keys` item. If no comparable keys remain for a scoped target pair, skip\n   those dependent checks for that pair.\n7. Same-repo repair: run the checks before editing, repair only localized\n   targets, preserve the original patch-derived scope through the final rerun,\n   recompute the comparable key subset from the final on-disk source\u002Ftarget\n   files after every edit, include any newly translated source-added keys in\n   that rebuilt comparable set, rerun the same relevant checks, then finish\n   with one independent read-only review before requesting any branch write.\n   Do not swap in a different guessed key set or reuse a stale pre-edit\n   comparable subset after a missing key has been added.\n8. Read-only review or fork guidance: stay read-only; cover every scoped target,\n   including real locales, not only pseudo-locales. Assess actual target-language\n   content rather than only key parity, parent-key lists, or checker bundles;\n   reject obvious English sentences, stubs, and provisional fallbacks unless a\n   declared exception applies. Report only the actual `PASS`, `FIXABLE`,\n   `BLOCKED`, or `INVALID_INPUT` outcomes plus concise human review.\n\n## Gotchas\n\n- The public checker API is file-only. Do not pass PR numbers, SHAs, repo\n  names, comparison-base discovery, or workflow `Mode` values.\n- `Test-RequiredKeys` can report missing entries and stale keys for a provided\n  source\u002Ftarget file pair, but it does not discover which untouched locale\n  files or deleted source-file counterparts must be inspected. The caller or\n  agent must do that repository discovery.\n- A clean working tree or a bare `git diff -- \u003Cfile>` can hide the authored\n  base-to-head change set you are supposed to review. Always inspect the full\n  `\u003Ccomparison-base> \u003Cimmutable-head>` patch when deriving scope.\n- `Test-SourceUnchanged`, `Gate`, and `Validate` are intentionally gone. Skip\n  decisions such as “formatting-only, do not spend AI” belong to the\n  caller\u002Fworkflow.\n- `Test-ResourceEncoding` is the only check that reasons about BOM\n  preservation. Keep source-preservation and safe-write policy in the caller,\n  and supply `-OriginalFile` whenever a comparison snapshot exists.\n- When batching in one process, carry forward genuine pre-edit snapshot paths\n  for existing files. If a file has no snapshot, omit `OriginalFile` rather\n  than pointing it at the rewritten file.\n- When the caller scopes keys, do not automatically reuse that same list for\n  `Test-PlaceholderParity`, `Test-LockedContent`, or `Test-PseudoLocale`.\n  Those APIs deliberately return `BLOCKED` when a scoped key is absent from the\n  source or target file. Use the full scoped list for `Test-RequiredKeys`, then\n  derive a comparable-only subset for the dependent checks.\n- Do not put source-removed names into scoped `-Keys` just to chase stale\n  target entries. That is explicit review-and-cleanup work from step 1. A\n  source-absent scoped key is a genuine `BLOCKED` input, not a fixable stale\n  entry.\n- If the entire scoped source\u002Ftarget file pair was removed and no current file\n  remains to feed the checker, materialize immutable pre-deletion snapshots for\n  those exact files and run syntax and encoding checks on the snapshots.\n  Treat the resulting bundles as historical evidence only, and separately use\n  git inspection to confirm that the live tree really removed the files.\n- After repairing a previously missing scoped key, recompute that\n  comparable-only subset from the final on-disk files before the final rerun.\n  A stale pre-edit empty comparable subset can incorrectly skip\n  placeholder, lock, or pseudo-locale validation for the new translated\n  source-added entry.\n- If your tool output truncates the original patch, keep reading until every\n  localization hunk has been seen. Never guess key scope from file names,\n  prefixes, or partial excerpts.\n- For in-process batching, use the dot-sourced public functions with a real\n  PowerShell key array such as `@('key1', 'key2')`. `-KeysJson` is only for\n  `pwsh -File` CLI calls.\n- When you invoke `localization_checks.ps1` from `pwsh -File`, use `-KeysJson`\n  for scoped keys. `-Keys key1,key2` is ambiguous at the CLI layer and is not\n  the supported script interface.\n- A source-only, blocked, or excluded-file result is not a successful repair.\n  Comment or fail honestly instead of pretending `PASS`.\n","# Ensure Localization\n\nUse this shared procedure for customer-facing localization. The caller supplies\nthe goal, scope, and permitted edits; PR or workflow context is not required.\n\n## Product consistency\n\nKeep terminology consistent within each locale and across RESW and localization\nYAML for the same product. Grammar may vary with context, but established product\nkeywords should not alternate between unrelated translations.\n\n## Language-quality acceptance\n\nFor every scoped customer-facing value in a real non-English locale, the final\ntext must actually be in that locale's target language. Copying the English\nsource or leaving a provisional English fallback is not a repair, even when all\nsix checks pass. English locales, source-authoritative locks, and legitimate\nidentical names or technical terms are allowed exceptions; translate the\nunlocked surrounding words.\n\n## Caller context\n\nThe caller owns repository or PR context, trusted revisions, skip policy,\nautomation allowlists, and safe-output rules. This skill owns only the reusable\nfile-based localization procedure.\n\n## Resources\n\n- File checker: [`.\u002Fscripts\u002Flocalization_checks.ps1`](.\u002Fscripts\u002Flocalization_checks.ps1)\n\n## Supported files\n\nThe skill applies to localization resources regardless of their location. The\nchecker supports `.resw` and flat locale `.yml` files; other YAML structures need\nan appropriate parser, not conversion merely to satisfy this checker.\n\nDiscover source and target files using the caller's context and existing layout.\nIn this repository, `en-US` files and direct resource files are common source\nauthorities; these are conventions, not mandatory checker paths.\n\nDo not edit source-authority files just to make translations pass.\n\n## Source-authoring guidance\n\n- Add translator context when wording is ambiguous or depends on UI usage, such\n  as a noun versus a command. Explain the meaning and placeholder roles; avoid\n  boilerplate comments for obvious strings.\n- Use `{Locked}` when the whole value must remain literal, and\n  `{Locked=\"token\"}` for invariant parts such as product names, protocol names,\n  commands, or paths. Use locale-scoped locks only when the exception genuinely\n  applies to those locales; do not exempt entire pseudo-locales by default.\n- Put guidance in the resource's `\u003Ccomment>` for RESW or its associated YAML\n  comment. Preserve annotations in target files where the format requires them.\n- When source edits are not permitted, report missing or contradictory source\n  guidance instead of silently changing source files or inventing meaning.\n  Mechanical checks preserve declared locks; they cannot decide which\n  annotations a new string needs.\n\n## Six checks\n\n| Check | Required args | Purpose |\n| --- | --- | --- |\n| `Test-ResourceSyntax` | `-File` | Parse supported XML or flat locale YAML shape |\n| `Test-ResourceEncoding` | `-File` (`-OriginalFile` optional) | Enforce UTF-8 and expected BOM behavior |\n| `Test-RequiredKeys` | `-SourceFile -TargetFile` (`-Keys` optional for PowerShell callers; CLI uses `-KeysJson` when scoping) | Missing and stale key parity |\n| `Test-PlaceholderParity` | `-SourceFile -TargetFile` (`-Keys` optional for PowerShell callers; CLI uses `-KeysJson` when scoping) | Placeholder identity and count parity |\n| `Test-LockedContent` | `-SourceFile -TargetFile` (`-Locale` sometimes required, `-Keys` optional for PowerShell callers; CLI uses `-KeysJson` when scoping) | Preserve locked values and tokens |\n| `Test-PseudoLocale` | `-SourceFile -TargetFile -Locale` (`-Keys` optional for PowerShell callers; CLI uses `-KeysJson` when scoping) | Catch English fallback and pseudo-style mistakes |\n\nExample commands:\n\n```powershell\npwsh .github\u002Fskills\u002Fensure-localization\u002Fscripts\u002Flocalization_checks.ps1 -Check Test-ResourceSyntax -File \u003Cfile>\npwsh .github\u002Fskills\u002Fensure-localization\u002Fscripts\u002Flocalization_checks.ps1 -Check Test-ResourceEncoding -File \u003Cfile> [-OriginalFile \u003Coriginal-file>]\npwsh .github\u002Fskills\u002Fensure-localization\u002Fscripts\u002Flocalization_checks.ps1 -Check Test-RequiredKeys -SourceFile \u003Csource-file> -TargetFile \u003Ctarget-file> [-KeysJson '[\"key1\",\"key2\"]']\npwsh .github\u002Fskills\u002Fensure-localization\u002Fscripts\u002Flocalization_checks.ps1 -Check Test-PlaceholderParity -SourceFile \u003Csource-file> -TargetFile \u003Ctarget-file> [-KeysJson '[\"key1\",\"key2\"]']\npwsh .github\u002Fskills\u002Fensure-localization\u002Fscripts\u002Flocalization_checks.ps1 -Check Test-LockedContent -SourceFile \u003Csource-file> -TargetFile \u003Ctarget-file> [-Locale \u003Clocale>] [-KeysJson '[\"key1\",\"key2\"]']\npwsh .github\u002Fskills\u002Fensure-localization\u002Fscripts\u002Flocalization_checks.ps1 -Check Test-PseudoLocale -SourceFile \u003Csource-file> -TargetFile \u003Ctarget-file> -Locale \u003Cpseudo-locale> [-KeysJson '[\"key1\",\"key2\"]']\n```\n\nThe script writes one JSON bundle to stdout and exits with the actual status\nmapping:\n\n- `0` → `PASS`\n- `20` → `FIXABLE`\n- `30` → `BLOCKED`\n- `64` → `INVALID_INPUT`\n\n## Batched checks\n\nFor larger scopes, use one `pwsh` process per batch: dot-source\n`localization_checks.ps1` once and call its public functions directly with\nnative PowerShell arguments. Assess the actual returned statuses and findings;\ndo not fabricate results or generate another checker.\n\nRun initial checks before repairs and rerun the affected checks after repairs.\nFor a read-only review, reuse successful check results instead of repeating the\nsame batch. Inspect summaries and non-PASS findings rather than printing every\nbundle into the model context. No separate aggregate checker-report file is\nrequired.\n\nThe agent owns scope completeness and language judgment. Mechanical checks\nsupport that assessment; they cannot establish that every affected resource\nwas discovered or that a translation is correct.\n\n## Reusable procedure\n\n1. Read the exact original localization patch content against the\n   caller-supplied immutable endpoints before choosing keys or counterpart\n   files. Use:\n   `git diff --no-ext-diff --unified=3 \u003Ccomparison-base> \u003Cimmutable-head> -- \u003Cresource paths>`.\n   Supporting summaries such as `git diff --stat`, `--name-only`,\n   `--name-status`, `--numstat`, `git status`, or a worktree-only\n   `git diff -- \u003Cfile>` are useful for discovery but are not sufficient to\n   derive scoped keys, values, or review coverage. If the diff output is\n   truncated, continue fetching the remaining hunks until you have read the\n   full patch for every relevant resource file. Derive the precise added or\n   updated source keys, values, and surrounding context from that exact patch;\n   do not infer scope from file prefixes, neighboring samples, unchanged source\n   lines, or PR summaries.\n   - Source-authority add or update: expand to every shipped localized\n     counterpart that should carry the affected file or keys, even when those\n     target files are unchanged in the git diff.\n   - Target-only edit: inspect that localized target against its source\n     authority.\n   - Source key or file removal: inspect obsolete shipped counterparts with\n     ordinary git and file review. Handle removal or cleanup explicitly instead\n     of claiming `PASS` because no file-pair check ran.\n2. Map each localized target to its source-authority file. In this repository,\n   `.resw` targets map to `...\u002FResources\u002Fen-US\u002F*.resw` or direct\n   `...\u002FResources\u002F*.resw`, and WTA locale targets map to\n   `tools\u002Fwta\u002Flocales\u002Fen-US.yml`.\n3. Before translating changed terms, inspect existing translations in the same\n   locale across both `.resw` files and `tools\u002Fwta\u002Flocales\u002F*.yml`. Reuse\n   established product terminology when the meaning and UI context match. If no\n   repository precedent exists, prefer Microsoft localized terms and flag\n   conflicting existing translations instead of inventing synonyms or rewriting\n   unrelated strings.\n4. Use `-Keys` only for native PowerShell function calls, or `-KeysJson` when\n   invoking the checker script from the CLI. Optional key scoping exists to\n   avoid fixing unrelated old debt, not to hide source additions that the\n   procedure already put in scope. Omit the scope parameter entirely for a\n   whole-file check.\n5. Run `Test-ResourceSyntax` and `Test-ResourceEncoding` on every file you\n   actually inspect.\n6. For each localized target, run `Test-RequiredKeys` against the full scoped\n   source-present change list, then run `Test-PlaceholderParity`,\n   `Test-LockedContent`, and, for pseudo-locales, `Test-PseudoLocale` only for\n   keys that are present in both the source-authority file and that target.\n   If a scoped key is missing on either side, keep the `Test-RequiredKeys`\n   finding and do not force the dependent checks across that absent entry. If\n   the source key or file was removed, handle that cleanup with step 1's\n   explicit review instead of treating the deleted source name as a scoped\n   `-Keys` item. If no comparable keys remain for a scoped target pair, skip\n   those dependent checks for that pair.\n7. Same-repo repair: run the checks before editing, repair only localized\n   targets, preserve the original patch-derived scope through the final rerun,\n   recompute the comparable key subset from the final on-disk source\u002Ftarget\n   files after every edit, include any newly translated source-added keys in\n   that rebuilt comparable set, rerun the same relevant checks, then finish\n   with one independent read-only review before requesting any branch write.\n   Do not swap in a different guessed key set or reuse a stale pre-edit\n   comparable subset after a missing key has been added.\n8. Read-only review or fork guidance: stay read-only; cover every scoped target,\n   including real locales, not only pseudo-locales. Assess actual target-language\n   content rather than only key parity, parent-key lists, or checker bundles;\n   reject obvious English sentences, stubs, and provisional fallbacks unless a\n   declared exception applies. Report only the actual `PASS`, `FIXABLE`,\n   `BLOCKED`, or `INVALID_INPUT` outcomes plus concise human review.\n\n## Gotchas\n\n- The public checker API is file-only. Do not pass PR numbers, SHAs, repo\n  names, comparison-base discovery, or workflow `Mode` values.\n- `Test-RequiredKeys` can report missing entries and stale keys for a provided\n  source\u002Ftarget file pair, but it does not discover which untouched locale\n  files or deleted source-file counterparts must be inspected. The caller or\n  agent must do that repository discovery.\n- A clean working tree or a bare `git diff -- \u003Cfile>` can hide the authored\n  base-to-head change set you are supposed to review. Always inspect the full\n  `\u003Ccomparison-base> \u003Cimmutable-head>` patch when deriving scope.\n- `Test-SourceUnchanged`, `Gate`, and `Validate` are intentionally gone. Skip\n  decisions such as “formatting-only, do not spend AI” belong to the\n  caller\u002Fworkflow.\n- `Test-ResourceEncoding` is the only check that reasons about BOM\n  preservation. Keep source-preservation and safe-write policy in the caller,\n  and supply `-OriginalFile` whenever a comparison snapshot exists.\n- When batching in one process, carry forward genuine pre-edit snapshot paths\n  for existing files. If a file has no snapshot, omit `OriginalFile` rather\n  than pointing it at the rewritten file.\n- When the caller scopes keys, do not automatically reuse that same list for\n  `Test-PlaceholderParity`, `Test-LockedContent`, or `Test-PseudoLocale`.\n  Those APIs deliberately return `BLOCKED` when a scoped key is absent from the\n  source or target file. Use the full scoped list for `Test-RequiredKeys`, then\n  derive a comparable-only subset for the dependent checks.\n- Do not put source-removed names into scoped `-Keys` just to chase stale\n  target entries. That is explicit review-and-cleanup work from step 1. A\n  source-absent scoped key is a genuine `BLOCKED` input, not a fixable stale\n  entry.\n- If the entire scoped source\u002Ftarget file pair was removed and no current file\n  remains to feed the checker, materialize immutable pre-deletion snapshots for\n  those exact files and run syntax and encoding checks on the snapshots.\n  Treat the resulting bundles as historical evidence only, and separately use\n  git inspection to confirm that the live tree really removed the files.\n- After repairing a previously missing scoped key, recompute that\n  comparable-only subset from the final on-disk files before the final rerun.\n  A stale pre-edit empty comparable subset can incorrectly skip\n  placeholder, lock, or pseudo-locale validation for the new translated\n  source-added entry.\n- If your tool output truncates the original patch, keep reading until every\n  localization hunk has been seen. Never guess key scope from file names,\n  prefixes, or partial excerpts.\n- For in-process batching, use the dot-sourced public functions with a real\n  PowerShell key array such as `@('key1', 'key2')`. `-KeysJson` is only for\n  `pwsh -File` CLI calls.\n- When you invoke `localization_checks.ps1` from `pwsh -File`, use `-KeysJson`\n  for scoped keys. `-Keys key1,key2` is ambiguous at the CLI layer and is not\n  the supported script interface.\n- A source-only, blocked, or excluded-file result is not a successful repair.\n  Comment or fail honestly instead of pretending `PASS`.\n",{"name":5,"description":7},"main","b83c3d762f8727f2ad299ddcc62fcf13bc7f35c7",".github\u002Fskills\u002Fensure-localization",179,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal","https:\u002F\u002Fdevblogs.microsoft.com\u002Fcommandline\u002Fannouncing-intelligent-terminal-version-0-1\u002F","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 22:29:46",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add microsoft\u002Fintelligent-terminal --skill ensure-localization",{"tool":60,"command":61},"bunx","bunx skills add microsoft\u002Fintelligent-terminal --skill ensure-localization",{"tool":63,"command":64},"pnpm","pnpm dlx skills add microsoft\u002Fintelligent-terminal --skill ensure-localization","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fensure-localization\u002FSKILL.md",true,[68,74,78,82],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"scripts\u002Flocalization_checks.ps1","SCRIPT","脚本",60658,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fensure-localization\u002Fscripts\u002Flocalization_checks.ps1",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"tests\u002FLocalizationChecks.Tests.ps1",37511,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fensure-localization\u002Ftests\u002FLocalizationChecks.Tests.ps1",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"tests\u002FLocalizationSummary.Tests.ps1",5939,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fensure-localization\u002Ftests\u002FLocalizationSummary.Tests.ps1",{"path":83,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":84,"sourceHtmlUrl":85},"tests\u002FLocalizationWorkflow.Tests.ps1",5638,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fensure-localization\u002Ftests\u002FLocalizationWorkflow.Tests.ps1",[87,124,153,175,208,233],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":91,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":103,"publishedAt":39},"01M69BS17H119AHC0VA6CGCG80","store-listing-localizer","Automate Microsoft Store (Partner Center) listing localization for Intelligent Terminal (Store ID 9NMQC2SSJX24). Use when asked to export\u002Fimport Store listings, localize release notes \u002F descriptions \u002F captions \u002F features into 80+ languages, update listingData CSV, or push Store listing translations without manually clicking through Partner Center. Drives Partner Center export\u002Fimport via the Playwright MCP and merges per-locale translations into the listingData CSV.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fstore-listing-localizer\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fstore-listing-localizer\u002FSKILL.md",[95,100],{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000004","电子表格","SCENARIO","使用场景",{"categoryNo":101,"categoryName":102,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000023","Skill与智能体开发",[104,105,106,107,108,109,9,110,111,112,113,114,115,116,117,118,119,120,20,121,122,123],"store listing localizer","listing","store","notes","playwright","terminal","update","release","release notes","MCP","Captions","localize","when","features","playwright mcp","listings","export","locale","automate","import",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":131,"publishedAt":39},"01M69BS54V1THPSKYAA7VFSBAY","upstream-sync","Periodically sync new commits from microsoft\u002Fterminal into this manually-forked intelligent-terminal repo by cherry-picking commit-by-commit onto a dated sync branch, auto-skipping revert pairs and empty commits, auto-resolving known take-upstream files, and stopping cleanly on genuine conflicts. The agent (you, reading this file) is the orchestrator — the PowerShell scripts are atomic operations you invoke one at a time. Use when the user asks to \"sync upstream\", \"pull from microsoft\u002Fterminal\", \"run upstream sync\", \"catch up to upstream\", or wires this into a scheduler (weekly\u002Fdaily). Designed to be safe under repeated unattended runs.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fupstream-sync\u002FSKILL.md",[130],{"categoryNo":101,"categoryName":102,"taxonomyType":98,"taxonomyTypeDesc":99},[132,133,134,135,109,9,136,137,138,139,140,141,142,143,144,145,146,147,116,148,149,150,151,152],"upstream sync","sync","upstream","run","sync upstream","safe","commit","weekly","branch","powershell","time","up","new","files","auto","invoke","you","one at a time","conflicts","catch","orchestrator",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":39},"01M69BRY6Z1T250VCQDTQ8ZFMQ","release-notes","Generate user-facing release notes for Intelligent Terminal. Use when asked to write release notes, changelog, what-is-new summary, or prepare a release. Compares git commits between releases, looks up PR-linked issues and community contributors, then outputs formatted notes with \"Verbed + Impact + Scenario\" style bullets, issue references, and contributor thanks.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Frelease-notes\u002FSKILL.md",[],[107,111,112,160,161,109,162,163,164,143,165,144,166,167,116,168,169,170,171,172,173,174],"pr","generate","git","prepare","community","issues","impact","contributor","references","changelog","releases","write","scenario","issue","contributors",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":188,"publishedAt":39},"01M69BRV95KH26NCNHGKX4BGTJ","pr-integration-test","Design, implement, and validate Intelligent Terminal integration tests for a target pull request or regression. Use when asked to add PR integration tests, convert a bug fix into E2E coverage, prove existing behavior still works, map tests to the release checklist, or verify E2E reports mark checklist cases complete.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpr-integration-test\u002FSKILL.md",[181,184,187],{"categoryNo":182,"categoryName":183,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":185,"categoryName":186,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":101,"categoryName":102,"taxonomyType":98,"taxonomyTypeDesc":99},[189,160,190,191,192,193,194,109,111,195,196,197,198,199,200,201,202,116,203,204,205,206,207],"test","pr integration test","integration test","integration","integration tests","pull request","validate","design","implement","coverage","regression","release checklist","fix","map","reports","request","bug","add","pull",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":215,"publishedAt":39},"01M69BRR7XQK0K0S4Z2Y81GX20","pr-accessibility","Review and repair native Windows WinUI, XAML, C++, UI Automation, keyboard, focus, screen-reader, high-contrast, scaling, settings, tab, pane, and agent-card accessibility changes. Use for accessibility analysis of Intelligent Terminal UI pull requests and focused local accessibility checks.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpr-accessibility\u002FSKILL.md",[214],{"categoryNo":101,"categoryName":102,"taxonomyType":98,"taxonomyTypeDesc":99},[160,216,217,218,219,220,221,109,222,30,223,224,225,226,227,228,229,230,231,232,207,28],"accessibility","pr accessibility","xaml","windows","pull requests","winui","automation","scaling","card","local","analysis","keyboard","focus","native","screen","contrast","ui",{"skillNo":234,"name":235,"nameZh":6,"description":236,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":237,"categories":238,"keywords":239,"publishedAt":39},"01M69BRNTFHGZ2CND9G3KWHPS7","performance-review","Review Intelligent Terminal performance changes in local work, commit ranges, branches, or PRs. Use for renderer, text-buffer, VT, UI-thread, tab\u002Fpane, WTA, async, session, logging, allocation, event-amplification, benchmark, profiling, responsiveness, memory, and CI-cost changes.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fintelligent-terminal\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fperformance-review\u002FSKILL.md",[],[240,241,30,242,109,243,138,244,225,245,246,247,248,249,232,250,251,252,253,254],"performance","performance review","memory","benchmark","ci","branches","buffer","text","work","allocation","logging","for","event","renderer","async"]