القائمة
Commit grain and the few deviations from the universal convention. Invoke before committing, splitting a workstream into commits, or auditing history.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
What to expose in settings surfaces and how to organize it. Invoke before exposing a setting, organizing a page, or reworking a settings surface.
Testing posture — test behavior not implementation, stay sober, grow coverage per workstream. Invoke before writing a test or extending coverage.
One normalized way to name files, folders, symbols, resources and providers. Invoke before naming or renaming.
How to write the JOURNAL.md. Invoke when recording a finding, or a small decision worth keeping.
What to observe in code, and how to write it readable and actionable. Invoke before adding or changing an observation point.
How versions are numbered and the changelog written. Invoke before cutting a version, writing a CHANGELOG entry, or drafting release notes.
| name | deckle-commits |
| description | Commit grain and the few deviations from the universal convention. Invoke before committing, splitting a workstream into commits, or auditing history. |
| type | skill |
Land the right commit grain and apply the handful of deviations from the universal convention. The universal Conventional Commits mechanics — format, type table, staging, safety — live in git-commit; this carries only what Deckle adds on top.
One commit = one self-contained intent — split aggressively, and each split must leave the repo compiling and coherent.
A scope names the module touched, one per commit; don't invent commit types, every change folds into the universal set.
Author identity — maintainer alone, never a Co-Authored-By: Claude trailer or a 🤖 Generated with… line. The temptation reappears exactly at commit time; it must never come back.
