commit-message

To write conventional commit messages from staged git changes, analyze the diff to determine the commit type, scope, and subject. The commit-message skill formats these staged changes into imperative subjects with rationale-focused bodies and breaking-change footers.

The best way to generate structured pull request descriptions from a branch diff is to document the summary, rationale, testing, and breaking changes. This skill drafts reviewer-ready PR descriptions directly from branch work, ensuring all critical context is covered.

To document breaking changes in commit messages and pull requests, add specific breaking-change footers to conventional commits and highlight them in the PR description. This skill enforces documenting these impacts to provide clear, durable records of intent and scope.

Yes, you can enforce branch naming conventions and commit hygiene for feature development workflows. This skill recommends workflow standards including atomic commits, branch naming matching the feature, and definition-of-done checks to maintain repository consistency.

A conventional commit is a standardized commit message format featuring types, scopes, and subjects, needed for code review to ensure intent is clear. You need it to provide reviewers with a durable record of scope, rationale, and verification for the changes.

Yes, this commit message formatter works with dependency updates and refactoring. It applies conventional commit formatting and structured PR documentation across feature development, bug fixes, refactors, documentation updates, and dependency changes.