القائمة
Draft commit summaries and bodies using this repo's Conventional Commit plus GNU-style file bullet format.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Run a bounded validation loop for current changes: tests, compile/checks, reviewer, verifier, fixes, then repeat until green or capped. Use when user asks to make changes green, run review and verify, 'until everything passes', or prepare a change for final validation.
Safely modify Zenit modules, autoloads, patches, and core/module boundaries.
Handle Zenit package declarations, package updates, and lockfiles.
Run and interpret Zenit Emacs tests through the project CLI.
استنادا إلى تصنيف SOC المهني
| name | zenit-commit-message |
| description | Draft commit summaries and bodies using this repo's Conventional Commit plus GNU-style file bullet format. |
| disable-model-invocation | true |
Use this skill when the user asks for a commit summary, commit message, or review of a proposed commit message.
docs/commit-messages.md for full messages..gitmessage for the concrete template.Summary:
type(component): Capitalized active-verb summary
Use the repo's Conventional Commit types. In addition to the usual types, this repo uses:
pkg for package/library/version changes.tweak for user-facing default changes that are not major features.Body entries use GNU-style bullets:
* file.el (symbol1, symbol2): Describe the change.
Add rationale or limitations when useful.
Ditto for repeated similar file changes.