localization-qa
Localization Qa
Overview
Use this skill to verify that localized experiences remain correct, usable, and release-safe across required locales.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Shared References
- Localization defect severity rules:
references/localization-defect-severity-rules.md
Templates And Assets
- Locale QA report template:
assets/localization-qa-report-template.csv
- Localization regression checklist:
assets/localization-regression-checklist.md
Inputs To Gather
- Required locale list and release scope.
- Localized strings, glossary, and style rules.
- UI builds/config for locale switching.
- Critical flows and compliance-sensitive copy.
Deliverables
- Locale-by-locale defect report with severity and ownership.
- Regression verification evidence for critical flows.
- Release recommendation with blocker summary.
- Follow-up retest plan for unresolved issues.
Workflow
- Confirm locale coverage and build readiness.
- Validate language and terminology correctness.
- Stress-test layout expansion/truncation/wrapping behavior.
- Validate locale formatting and directional behavior.
- Record findings in
assets/localization-qa-report-template.csvand close withassets/localization-regression-checklist.md.
Quality Standard
- Required locales are fully covered.
- Critical flows pass with no blocker-level localization defects.
- Severity reflects user/business impact across locales.
- Defect ownership and retest status are explicit.
Failure Conditions
- Stop release recommendation when required locale coverage is incomplete.
- Stop when blocker-level semantic or layout defects remain unresolved.
- Escalate when localization defects affect legal/compliance-critical content.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9