基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/RocketChat/Rocket.Chat.Electron --skill release-notes命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 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 | release-notes |
| description | Generate release notes from git history between tags |
Generate categorized release notes from git commit history between two tags or refs.
from (optional): Starting tag/ref. Defaults to the previous tag.to (optional): Ending tag/ref. Defaults to HEAD.If from is not provided, find the most recent tag:
git describe --tags --abbrev=0 HEAD~1
If to is not provided, use HEAD.
git log --oneline --no-merges <from>..<to>
Parse commit messages using conventional commit prefixes and categorize:
| Prefix | Category |
|---|---|
feat: | New Features |
fix: | Bug Fixes |
perf: | Performance |
refactor: | Improvements |
chore: | Maintenance |
docs: | Documentation |
ci: | CI/CD |
test: | Testing |
Commits without conventional prefixes go under "Other Changes".
## What's Changed
### New Features
- Description of feature (#PR)
### Bug Fixes
- Description of fix (#PR)
### Improvements
- Description of improvement (#PR)
### Maintenance
- Description of chore (#PR)
Detect the version type from package.json and note:
X.Y.Z-alpha.N): Mark as "Alpha Release - For QA and early testing"X.Y.Z-beta.N): Mark as "Beta Release - Pre-release testing"X.Y.Z): Mark as "Stable Release"Present the formatted release notes to the user for review. Do not create any files unless asked.