--- name: commit scope: universal description: | Format commit messages following conventional commits standard. Use when: writing commit messages, git commit, reviewing commit history. Keywords: commit, git, message, conventional, feat, fix, refactor. --- # Commit Message Standards > **Language**: English | [繁體中文](../../locales/zh-TW/skills/commit-standards/SKILL.md) **Version**: 1.0.0 **Last Updated**: 2025-12-24 **Applicability**: Claude Code Skills --- > **Core Standard**: This skill implements [Commit Message Guide](../../core/commit-message-guide.md). For comprehensive methodology documentation, refer to the core standard. ## Purpose This skill ensures consistent, meaningful commit messages following conventional commits. # [Physical Binding] ## Reality Check Before submitting the commit message, you MUST: 1. Verify Environment: Run `uds check --standard commit-message` to ensure `commitlint` is configured. 2. Verify Content: Run `echo "{message}" | npx commitlint` to validate the generated message. 3. IF exit_code != 0: - Read the error message. - REVISE the message. - RETRY validation until it passes. ## Quick Reference ### Basic Format ``` ():