菜单
Generate a formatted Slack message to share a pull request with the team. Use when the user asks to generate a Slack message for a PR, share a PR on Slack, or after creating a pull request.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/LedgerHQ/ledger-live --skill slack-pr-message命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | slack-pr-message |
| description | Generate a formatted Slack message to share a pull request with the team. Use when the user asks to generate a Slack message for a PR, share a PR on Slack, or after creating a pull request. |
Generate a formatted Slack message to announce a pull request.
:pr-open: {{PREFIX}} - {{SHORT_DESCRIPTION}}
{{PR_URL}}
| Impacted packages | Prefix |
|---|---|
live-mobile only | LWM |
ledger-live-desktop only | LWD |
@ledgerhq/live-common or shared libs | Common |
| CI, scripts, developer tooling | Tooling |
Both live-mobile and ledger-live-desktop | LWM + LWD |
When multiple non-app packages are impacted alongside an app, use the app prefix. Combine prefixes only when both apps are affected.
:pr-open: LWM - Add portfolio analytics dashboard
https://github.com/LedgerHQ/ledger-live/pull/1234
Place and organize Ledger Wallet code in the DDD monorepo. Use when creating, moving, or reviewing code under apps, features, domain, shared, or support; deciding which layer owns a concern; structuring packages and flow steps; or checking package names, dependency boundaries, platform variants, and legacy imports.
A new-architecture package (shared/, domain/, features/) exposes its API through barrels that contain nothing but `export *`, and keeps its private code in an internals location. Read this when creating a package under shared/, domain/ or features/, when editing any `index.*` file, or when a `lint:structure` check fails.
A new-architecture package (shared/, domain/, features/) exposes its API through barrels that contain nothing but `export *`, and keeps its private code in an internals location. Read this when creating a package under shared/, domain/ or features/, when editing any `index.*` file, or when a `lint:structure` check fails.
基于 SOC 职业分类
