| name | commit-formatter |
| description | Format commit messages following Conventional Commits — works in terminal and IDE |
| version | 2.0.0 |
| compat | claude-code, codex, cursor, openclaw |
| fill | co-authored-by |
Skill: Commit Formatter (History Standardization)
Purpose
Guarantee that every commit in the Git history strictly follows the Conventional Commits specification. This enables human readability, clean forensic audits, and future automation of release notes.
General Format Rules
<type>(<optional scope>): <short description in lowercase, imperative mood>
[Optional body: What changed and why, never HOW]
[Optional footer: BREAKING CHANGE or Issue/Task references]
Critical Restrictions
- Length: The first line (header) must never exceed 72 characters.
- Case: The short description starts strictly in lowercase and has no period at the end.
- Body Content: Explain the business context or engineering decision. The code already shows the how.
Allowed Types
| Type | Usage Criteria |
|---|
feat | New functionality directly for the user or system. |
fix | Bug fix or anomalous behavior correction. |
refactor | Code modification that doesn't add features or fix bugs (cleanup). |
test | Adding, modifying, or fixing unit/integration tests. |
docs | Documentation, Markdown, or comments only. |
chore | Maintenance tasks: dependency updates, scripts, configs. |
perf | Code optimization focused purely on performance/memory. |
ci | CI/CD pipeline or deployment flow changes. |
Orchestration Flow
In Claude Code / Codex / Cursor (Terminal)
The agent automates the commit after passing the Build Check by:
git add . (or selected files).- Generating the message under this standard.
- Adding the authorship footer if applicable:
{{FILL: If this project uses commits from an AI agent, optionally add:
Co-Authored-By: [Agent Name] <noreply@[domain].com>
Examples: Claude AI <noreply@anthropic.com>, GitHub Copilot <noreply@github.com>
If not applicable, omit this line.
}}
In IDE (Antigravity, VS Code with AI)
The integrated agent reads this file and processes the Staged Changes area:
- Analyzes the current diff in the side panel.
- Writes the formatted message directly into the Git commit text field.
- Lets the user click the native "Commit" button with pre-validated text.
