{"slug": "semantic-commit-messages", "title": "Semantic Commit Messages", "summary": "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.", "body_md": "See how a minor change to your commit message style can make you a better programmer.\nFormat: <type>(<scope>): <subject>\n<scope>\nis optional\nfeat: add hat wobble\n^--^ ^------------^\n| |\n| +-> Summary in present tense.\n|\n+-------> Type: chore, docs, feat, fix, refactor, style, or test.\nMore Examples:\nfeat\n: (new feature for the user, not a new feature for build script)fix\n: (bug fix for the user, not a fix to a build script)docs\n: (changes to the documentation)style\n: (formatting, missing semi colons, etc; no production code change)refactor\n: (refactoring production code, eg. renaming a variable)test\n: (adding missing tests, refactoring tests; no production code change)chore\n: (updating grunt tasks etc; no production code change)\nReferences:", "url": "https://wpnews.pro/news/semantic-commit-messages", "canonical_source": "https://gist.github.com/joshbuchea/6f47e86d2510bce28f8e7f42ae84c716", "published_at": "2017-05-15 22:41:29+00:00", "updated_at": "2026-05-22 10:43:47.295455+00:00", "lang": "en", "topics": ["developer-tools"], "entities": [], "alternates": {"html": "https://wpnews.pro/news/semantic-commit-messages", "markdown": "https://wpnews.pro/news/semantic-commit-messages.md", "text": "https://wpnews.pro/news/semantic-commit-messages.txt", "jsonld": "https://wpnews.pro/news/semantic-commit-messages.jsonld"}}