git-commit-formatter

Conventional commit formatting structures messages with a type (feat, fix, docs, etc.), summary line, and optional body. This skill analyzes your staged changes and git history to generate properly formatted commit messages that classify changes consistently, enforce a concise first line, and include a Claude Code signature for transparency and traceability.

A conventional commit is a standardized format for git commit messages that includes a type, scope, and description. Conventional commits improve code review clarity, generate readable project history, and enable automated release notes and version bumping—making collaboration and change tracking predictable across teams.

Yes. This skill automatically analyzes staged changes and diffs to draft conventional commit messages for feature, fix, documentation, style, refactor, test, chore, and performance changes. It enforces consistent structure, applies safety checks to prevent secrets, and stages changes via heredoc for a complete workflow.

This skill integrates into your existing workflow after you stage changes. It reads git status, diffs, and recent history to propose formatted messages. You review and confirm before committing, maintaining full control while eliminating manual formatting and ensuring all commits meet conventional standards.

The skill includes safety checks to detect and avoid committing secrets or sensitive data. It also enforces a first-line length guideline, validates commit type classification, and provides a transparent signature indicating Claude Code generation—giving you confidence in what's being committed.