Conventional Commits

**Judgement:** A focused, high-quality skill for enforcing the Conventional Commits standard in commit messages. Well-suited as a default helper whenever an agent is asked to write or polish git commit messages. **Strengths:** - Encodes the core Conventional Commits rules (types, scopes, imperative descriptions, bodies, footers, breaking changes) in a clear, operational way. - Pairs naturally with tools that rely on Conventional Commits for semantic versioning and changelog generation. - Very safe and lightweight: it only formats text and can be broadly enabled without risk to code or data. **Key Risks / Limitations:** - Not all repositories use Conventional Commits; blindly enforcing it may conflict with project-specific commit guidelines. - May over-normalize user style (e.g., non-English descriptions or custom type keywords) if the agent isn’t instructed to respect local conventions. - Does not itself interact with git or manage commits; it only formats the message string. **Recommended Scenarios:** - Teams or projects that have adopted Conventional Commits and want consistent commit history. - Workflows that use semantic-release or similar tools where correct commit typing directly affects version bumps and changelog generation. - Any agent configuration that often writes commit messages, PR merge messages, or advises on git workflows, especially in CI/CD and release engineering contexts.