git-commit

To generate conventional commit messages, the Skill analyzes your git status and git diff of staged changes to produce a descriptive subject, an optional body, and a Co-authored-by footer. It ensures clear, atomic commits without performing destructive staging actions.

Writing atomic git commits is facilitated by analyzing the staged diff and advising on splitting large changes into multiple focused commits. This ensures your version control history remains clean, consistent, and focused on individual logical changes.

Yes, you can use conventional commits to standardize your project's git history. The Skill enforces the conventional commit standard by crafting well-formed messages with descriptive subjects and optional bodies, streamlining clarity across the development timeline.

Crafting commit messages with this approach requires existing staged changes, as it analyzes git status and git diff. It strictly avoids staging or other destructive actions without explicit permission, meaning you must stage your files manually first.

To include co-authorship information in git commit messages, the Skill automatically appends a Co-authored-by footer when collaborating. It analyzes your staged changes to generate the complete conventional commit message with the appropriate attribution.

You should split large changes into multiple conventional commits when the staged diff encompasses multiple logical changes. The Skill advises on this separation to maintain atomic commits, ensuring each message accurately describes a single, focused update.