commit

Split git changes by grouping related edits into separate commits using conventional prefixes and scope. This organizes feature work, bug fixes, and documentation into a clean, auditable history where each commit contains only the changes described.

Git commits bundle unrelated changes when work isn't split by purpose. This skill solves that by enforcing conventional commit prefixes and structured messages, ensuring each commit contains only the changes described and groups related edits logically for better traceability.

Organize version control history by splitting changes into focused commits with conventional prefixes. This creates a clean, auditable history that improves code review traceability and supports release notes generation through structured commit messages.

Conventional commit workflow works for bug fixes, documentation, and feature work by applying structured prefixes and scope to each commit. It targets software development tasks specifically, ensuring each commit contains only the changes described for clean audit trails.

You can use focused conventional commits for generating release notes from commit history. By enforcing structured messages with conventional prefixes and scope, the skill creates an auditable history that supports release notes, code reviews, and audit trails.

You should not use conventional commit prefixes when your changes are too small to warrant structured messages or when working outside version control workflows. This skill targets software development tasks like feature work, bug fixes, and documentation that benefit from auditable history.