| name | terse-semantic-commits |
| description | Write semantic commit messages in Conventional Commits format. Use when committing, writing commit messages, or when a terse semantic commit is required. Covers format, types, scope, imperative mood, and length. |
Terse Semantic Commits Skill
Produce commit messages that follow Conventional Commits: terse, semantic, imperative. See CONTRIBUTING.md and AGENTS.md for project standards.
When to Use
- Use when committing changes and a commit message is needed
- Use when a terse semantic commit is required (e.g. commit workflows, PR creation)
Format
<type>(<scope>): <description>
- type: Required. One of: feat, fix, docs, style, refactor, perf, test, chore, ci, build, revert
- scope: Optional but recommended. Area affected (lowercase)
- description: Required. Imperative mood, lowercase, no trailing period, terse (under ~50 chars)
Rules
- Imperative mood: "add" not "added" or "adds"
- Lowercase description, no trailing period
- Derive type/scope from changed files and edits (e.g.
auth/ → scope auth)
- One commit message per staged group when used with stage-related-files
- Use only
git commit -m "..." for the message; do not use --trailer
Examples
- Good:
feat(api): add user search endpoint, fix(auth): resolve token expiry bug
- Bad:
Added new feature, Update files, Fixed the bug
Related Artifacts
