菜单
Gitmoji + Conventional Commits convention for this repo (commit messages, branch names, and PR titles), enforced by the Danger CI bot. Use whenever creating commits, invoking /commit, naming a branch or PR, or fixing messages that failed Danger.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/LedgerHQ/ledger-button-public --skill commit命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Gitflow backmerge workflow that brings release changes from main back into develop. Use whenever the user says "backmerge", "back-merge", "merge main into develop", or invokes /backmerge. Do not improvise the steps — follow this procedure exactly.
End-to-end release workflow to cut and publish a new version (consume version plans, bump versions, update changelogs, open the release PR against main). Use whenever the user asks to do a release, cut a version, publish packages, or invokes /release. Do not improvise the steps — follow this procedure exactly.
基于 SOC 职业分类
正在显示 SKILL.md
| name | commit |
| description | Gitmoji + Conventional Commits convention for this repo (commit messages, branch names, and PR titles), enforced by the Danger CI bot. Use whenever creating commits, invoking /commit, naming a branch or PR, or fixing messages that failed Danger. |
| alwaysApply | false |
Create a commit following the project's gitmoji + Conventional Commits conventions (enforced by tools/danger/helpers.ts). This same format applies to commit messages, branch names, and PR titles.
<emoji> (<scope>) [<TICKET>]: <Description>
<emoji> — one gitmoji from the table below.<scope> — lowercase module/package (e.g. ledger-button, ledger-button-core, ci, release, docs, version).[<TICKET>] — LBD-<number> (uppercase in brackets), NO-ISSUE, or ISSUE-<number>. Always include it: Danger only enforces it on PR titles, but the convention is to include it on every commit too so the squash-merge history stays consistent.<Description> — starts with an uppercase letter.Examples (matching real commits on develop):
✨ (ledger-button-core) [LBD-563]: Add normalizeAddressForCurrency seam
🐛 (ledger-button) [LBD-560]: Resolve token icons via Ledger CDN
🔖 (version) [LBD-369]: Add version plan
🔧 (release) [NO-ISSUE]: Fix build snapshot workflow
👷 (ci) [NO-ISSUE]: Use SONAR_TOKEN secret
| Type | Emoji | Code |
|---|---|---|
| Feature | ✨ | :sparkles: |
| Bug fix | 🐛 | :bug: |
| Refactor | ♻️ | :recycle: |
| Documentation | 📝 | :memo: |
| Tests | ✅ | :white_check_mark: |
| Performance | ⚡ | :zap: |
| Breaking change | 💥 | :boom: |
| Chore / config | 🔧 | :wrench: |
| Dependencies | ⬆️ | :arrow_up: |
| Remove code | 🔥 | :fire: |
| Style / format | 🎨 | :art: |
| Types | 🏷️ | :label: |
| CI | 👷 | :construction_worker: |
| Lint fixes | 🚨 | :rotating_light: |
| Version plan | 🔖 | :bookmark: |
Check staged changes — Run git status and git diff --staged to understand what will be committed.
Gather required information — Ask the user for anything that cannot be inferred:
ledger-button, test-dapp, docs)LBD-<number>, ISSUE-<number>, or NO-ISSUECreate the commit:
git commit -m "<emoji> (<scope>) [<TICKET>]: <Description>"
If there are multiple logical changes, create atomic commits for each.
If the user provides context after the command (e.g., /commit fix login button not responding), use it to:
Format: <prefix>/<ticket-lowercase>-<kebab-description>
Allowed prefixes (from BRANCH_PREFIX in tools/danger/helpers.ts): feature / feat, bugfix / bug / hotfix / fix, support, chore / core / task, doc, refacto / refactor.
Examples:
feat/lbd-369-add-v2-dapp-config-use-casebugfix/lbd-123-fix-redirectchore/no-issue-bump-eslintpnpm commit — interactive commit prompt.pnpm danger:local — validate branch name + commits + PR title locally.