commit message

basicwidespread

A commit message is a short text note explaining what and why someone changed in the program code at a specific save point.

In plain terms

Imagine a ship's log: the captain records what happened and why a decision was made at every important event. In software development, a commit message serves the same purpose: when someone saves a code modification (the commit), they write a few lines explaining what they did.

It is useful for determining months or years later why the program looks the way it does. The code itself only shows what changed; the intent is preserved in the message.

Humans no longer write code alone. Coding agents usually compose commit messages for their modifications themselves, so you can trace what the AI did on your behalf from these messages and the changes themselves.

How it works

The developer or the coding agent modifies some files, then selects which changes belong together.
When saving (commit), the version control system, most often Git, requests a text note: this is the commit message.
The message usually consists of a short, subject-line-style summary, and if needed, a few sentences below detail the reasons.
The system permanently stores the message along with the author's name, timestamp, and exact changes.
Later, anyone can scroll through the message history to find which modification caused a bug or introduced a new feature.

An everyday example

You ask a coding agent to fix an incorrect VAT calculation in your online store's cart. At the end of the work, you see this in the log: "Fix: VAT rounding on the cart total." This line is the commit message, telling you what was changed.

Who is affected

developerIt writes and reads such messages daily, and from these it understands the previous decisions of colleagues or the agent. → Code

entrepreneur, executiveFrom the message log, one can roughly follow what the team or the AI agent worked on without programming knowledge.

jobseeker, new graduateIn public repositories, their messages are visible too, and employers can also infer from them how carefully they work. → Work & HR

A common misconception

MythThe commit message is unnecessary administration since the code shows what changed anyway.

In realityOnly the changes in the code are visible, not the reasons behind them. The commit message preserves the rationale, often serving as the only explanation years later for a seemingly odd solution.

Limits and risks

A message is only worth as much as it is precise: text like 'fix' or 'changes' reveals nothing.
An agent-written message can confidently claim something the code does not actually do, so it is important to review the modification itself during significant changes.
The shared commit message is difficult to alter unnoticed afterward, so do not include passwords, customer data, or other confidential information.
It does not replace documentation: it explains individual steps, not the entire system.

Similar, but not the same

commit – The commit itself is the saved change package; the commit message is only the attached textual explanation.
code comment – A comment is a note written between lines of code that lives with the code, while a commit message belongs to the history of the change.
changelog – A changelog is a release-by-release summary for users, while a commit message is a step-by-step record for developers.

Related concepts

Broader

version control, Git, software development

Narrower

Conventional Commits, subject line

On the edge

commit, code repository, pull request, code review, coding agent

A brief history

The note attached to changes appeared alongside version control systems: the SCCS system of the 1970s, followed by RCS, CVS, and Subversion, all required such text for every save. The most widely used system today, Git, was launched by Linus Torvalds in 2005 for Linux kernel development. The current standard format—a short subject line, an empty line, then detailed text—spread from the Linux kernel's email patch submission practice.

Where things stand

At the end of 2026, the commit message is an everyday basic tool of software development. An increasing share of them is written by coding agents and AI assistants; in such cases, it is the human's job to check and approve.

Status: 2026 November

Also known as

commit message · commit message · commit message · commit message · commit msg · commit message · commit message

Sources

This entry was machine-edited and has undergone machine expert review; the “In the news” section updates automatically from Agent Age stories.