基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/RocketChat/Rocket.Chat.Electron --skill i18n-audit命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Drive and screenshot the running Rocket.Chat Desktop dev app (yarn start) through the main-process inspector on port 9339 — trigger menu items (Simulate Download/Update), evaluate in the renderer DOM, capture titlebar screenshots. Use whenever a UI change needs runtime/visual verification that component tests can't see (paint, clipping, colors, animation, layout).
Ship a Rocket.Chat.Electron release end-to-end. Collects merged fixes since the last tag, drafts release notes, bumps the version on a chore/release branch, opens the bump PR, and — after explicit user approval at each gate — merges, tags, monitors the build-release pipeline in the background, and verifies the published release has the full platform asset matrix. Handles alpha (on dev), stable promotion (dev→master), and patch releases (release/X.Y.x). Trigger when the user says "ship release X.Y.Z", "release 4.16.0", "cut a patch release", "promote alpha to stable", or "/ship-release".
Upgrade the Electron version in Rocket.Chat.Electron safely. Detects breaking changes between the current and target Electron release, produces a migration plan gated on user approval, applies the fixes (using GitNexus impact analysis to find every affected callsite), bumps coupled config (electron-builder bundle id, CI node-version, @types/node), runs lint + tests, and opens a ready PR from a fresh branch off dev. Trigger when the user says "bump electron", "upgrade electron", "update electron to X", "/electron-bump", or asks to move to a newer Electron release.
| name | i18n-audit |
| description | Audit translation completeness across all language files |
Compare all language files against the English reference (src/i18n/en.i18n.json) and report translation coverage.
language (optional): Audit a specific language code (e.g., pt-BR, ja). Defaults to all languages.verbose (optional): If "true", list every missing key. Otherwise show summary only.Read src/i18n/en.i18n.json and extract all keys (including nested keys using dot notation, e.g., dialog.about.title).
For each *.i18n.json file in src/i18n/ (except en.i18n.json):
en but absent in this languageen (possibly outdated)Output a summary table:
Language | Keys | Missing | Extra | Coverage
-------------|------|---------|-------|--------
pt-BR | 142 | 3 | 0 | 97.9%
ja | 138 | 7 | 1 | 95.2%
...
If verbose is "true", also list the specific missing and extra keys per language.
Flag any language below 90% coverage as needing attention.
The project has 22 language files: ar, de-DE, en (reference), es, fi, fr, hu, it-IT, ja, nb-NO, nn, no, pl, pt-BR, ru, se, sv, tr-TR, uk-UA, zh, zh-CN, zh-TW