# Git Commit Message > Generates git commit messages according to werf conventions. Use after staging changes. - Skill: `tomevault-io/git-commit-message` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/git-commit-message` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/git-commit-message/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/git-commit-message --- # Git Commit Message Generation ## Instructions 1. Read types, scopes, subject rules, and body rules from `CONTRIBUTING.md#conventions`. 2. Analyze `git diff --cached` to determine the primary type and scope. 3. Use the following format: ``` (): ``` 4. Follow these rules: - **Header:** ≤ 72 characters. Nested scopes are allowed. - **Subject:** imperative, lower-case, no trailing period. - **Body:** imperative, include motivation for the change, contrast with previous behavior. 5. Output ONLY the commit message (header + body), with no additional text, quotes, or formatting. --- > Source: [werf/werf](https://github.com/werf/werf) — distributed by [TomeVault](https://tomevault.io).