菜单
Generates a Conventional Commits message with a What/Why/Impact body for ClearSync, per RO-002. Use when the user asks to "write a commit message", "commit this", "generar un commit", or before creating a commit in this repo.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ergrato-dev/obsidian-clearsync --skill commit-message命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | commit-message |
| description | Generates a Conventional Commits message with a What/Why/Impact body for ClearSync, per RO-002. Use when the user asks to "write a commit message", "commit this", "generar un commit", or before creating a commit in this repo. |
Follow RO-002 (docs/{es,en}/requisitos/restricciones.md): every commit uses
Conventional Commits, with a body covering What, Why, and Impact — not
just a summary of the diff.
<type>(<scope>): <imperative summary, ≤72 chars>
What: <what changed, one or two sentences>
Why: <why this change was needed — the actual motivation, not "to improve X">
Impact: <what this unblocks, fixes, or changes for users/contributors>
<type>: feat, fix, docs, refactor, test, chore, perf, security.
<scope> (optional): the module — sync-engine, crypto, settings-ui,
dropbox-provider, docs, etc.
Impact: implements RF-003 automatic three-way merge.docs: type, still fill What/Why/Impact — a docs
change has a reason too, not just a description of what got added.Co-Authored-By:), not the message body.