메뉴
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에서 현재 제공할 수 있는 파일을 다운로드하세요.
Creates a new bilingual (es/en) functional requirement (RF) document for ClearSync, following the project's standard RF template (Identificación, Descripción, Entradas, Proceso, Salidas, APIs/Componentes involucrados, Reglas de negocio). Use when the user asks to "add a new RF", "document a new feature", "crear un RF nuevo", or before implementing any functional change not yet covered by an existing RF (required by RO-003).
Checklist for implementing a new SyncProvider (e.g. WebDAV, S3, Google Drive) in ClearSync, respecting the Strategy pattern interface and the project's security/RNF constraints. Use when the user asks to "add a new sync provider", "implement WebDAV support", "agregar un proveedor de sync", or similar.
OWASP-aligned security checklist for reviewing ClearSync code changes, covering encryption, token handling, path safety, and conflict-resolution integrity. Use when the user asks for a "security review", "revisión de seguridad", or before merging any change that touches auth, crypto, or the sync pipeline.
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.