conventional-commits

What This Skill Does

The conventional-commits skill is a powerful automation utility designed for OpenClaw AI to standardize project versioning and history. It enforces the Conventional Commits specification, a lightweight convention on top of commit messages. By providing a structured set of rules for commit headers, footers, and types, this skill enables your repository to automatically generate changelogs, derive semantic versions, and improve overall team communication. It serves as a strict validator and formatting assistant, ensuring that every commit message conveys clear intent regarding the change, whether it is a feature, a bug fix, or a breaking API change.

Installation

To integrate this skill into your environment, use the OpenClaw command-line interface. Run the following command in your terminal: clawhub install openclaw/skills/skills/bobdevibecoder/bobagent-conventional-commits Once installed, OpenClaw will automatically monitor your commit workflows and prompt or auto-format messages according to the standard.

Use Cases

• Automated Release Management: Use this skill to ensure your repository is ready for tools like semantic-release, which analyze commits to determine if the next version should be a patch, minor, or major update.
• Team Onboarding: Ensure that new developers contribute to the codebase with high-quality, readable histories that are easy to audit.
• Project Maintenance: Quickly generate accurate documentation of changes for stakeholders by leveraging the structured metadata provided by the commit types (feat, fix, docs, chore, etc.).

Example Prompts

1. "I just fixed the login bug in the auth module, please write a conventional commit message for me."
2. "Can you help me format this change as a breaking change commit? I refactored the database schema and it will break existing production tables."
3. "Summarize my recent work in the parser folder and generate a feat-type commit message for the new array parsing logic."

Tips & Limitations

• Imperative Mood: Always use imperative verbs (e.g., "add" instead of "added").
• Breaking Changes: Always use the ! suffix or the BREAKING CHANGE: footer for any modification that requires users to change their code.
• Scope usage: Don't overuse scopes; keep them restricted to specific modules or sub-directories for maximum clarity.
• Limitations: While this skill aids in formatting, it cannot judge the internal quality of the code itself. Always review the generated message before applying to ensure it accurately reflects the depth of the work performed.