format-commit-message

Conventional commits follow a {type}({scope}): {description} structure. This Skill formats your commits automatically, enforcing valid types, lowercase scopes, and wrapping text at 72 characters to ensure consistency across your project.

Yes. This Skill includes generated-by lines and Co-Authored-By metadata to attribute commits to Claude Code, useful for tracking automated changes and contributions across your repository.

Breaking changes are pushed to commit footers with BREAKING CHANGE notes. This Skill validates and formats breaking-change handling automatically when you mark a commit as breaking.

Conventional commit validation enforces valid commit types, requires a description, enforces lowercase scopes, prevents trailing periods, and ensures proper structure. This Skill applies all rules automatically to maintain consistency.

Conventional commits standardize release commits, automated version updates, refactors, and documentation changes. Use this approach when your team needs consistent formatting, automated changelog generation, or semantic versioning across projects.

Yes. This Skill applies conventional formatting to release commits and automated version updates, ensuring generated commits follow the same standards as manual ones and integrate seamlessly with CI/CD pipelines.