A commit summary is the short subject line describing the change recorded by a version-control commit. It is useful as a compact signal, but it is not reliable evidence of the change by itself. section 6.4
Use summaries to profile development work, while checking their claims against code-level evidence. A practical record combines month, author, scope, and subject, then anchors interpretation with landmark diffs. section 6.4
A commit-summary record
A history-analysis input might contain: “month | author | scope | subject.” For example, the subject identifies the change briefly, while a sampled opening, peak, or closing diff tests whether that description reflects the implementation. section 6.4
