Formatting Commit Messages

What it does

This skill automatically formats commit messages according to conventional commits standards. It ensures that commit messages adhere to a consistent structure, including a type (e.g., feat, fix, docs), scope (optional), and description. This improves code review efficiency and facilitates automated versioning processes.

When to use it

• When preparing commit messages for projects following conventional commits guidelines.
• To enforce consistency in commit message formatting across a development team.
• Before pushing changes to repositories that require standardized commit messages (e.g., those using semantic release).
• During automated workflows where commit message parsing is necessary.

Key capabilities

• Conventional Commits Formatting: Adheres to the conventional commits specification.
• Type, Scope, and Description Parsing: Extracts and formats these components of a commit message.
• Automated Message Generation (implied): Can likely generate messages based on provided context.

Example prompts

• "Format this commit message: 'Fixes bug in user authentication.'"
• "Generate a conventional commit message for adding a new feature to the payment processing module."
• "Ensure this commit follows conventional commits standards: 'Updates documentation'."

Tips & gotchas

• Requires familiarity with conventional commits conventions. The skill will likely not automatically determine the correct type or scope without guidance.