cd /news/developer-tools/semantic-commit-messages · home topics developer-tools article
[ARTICLE · art-8432] src=gist.github.com ↗ pub= topic=developer-tools verified=true sentiment=· neutral

Semantic Commit Messages

Structured format for writing Git commit messages: `<type>(<scope>): <subject>`. It explains that using specific types like `feat`, `fix`, or `docs` in the message makes the commit's purpose clear and improves programmer communication. The guide notes that the scope is optional and that the subject should be written in the present tense.

read1 min views19 publishedMay 15, 2017

See how a minor change to your commit message style can make you a better programmer. Format: <type>(<scope>): <subject> <scope> is optional feat: add hat wobble ^--^ ^------------^ | | | +-> Summary in present tense. | +-------> Type: chore, docs, feat, fix, refactor, style, or test. More Examples: feat : (new feature for the user, not a new feature for build script)fix

: (bug fix for the user, not a fix to a build script)docs
: (changes to the documentation)style
: (formatting, missing semi colons, etc; no production code change)refactor

: (refactoring production code, eg. renaming a variable)test

: (adding missing tests, refactoring tests; no production code change)chore
: (updating grunt tasks etc; no production code change)

References:

── more in #developer-tools 4 stories · sorted by recency
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/semantic-commit-mess…] indexed:0 read:1min 2017-05-15 ·