World 1: Save Points

Good commit messages

You will learn: how to write commit messages that still make sense next month.

The problem

~/diary $ git log --oneline1ad5b54 (HEAD -> main) fix40c183b asdfa4bd293 update43b5fc4 stuff6d3a9b1 Add README

A month later, you read your log. Which commit added the about page? Nobody knows. Not even you.

Watch

A good commit message says what changed. Keep it short: aim for 50 characters or less.

Watch

Start with an action word, like an order: Add, Fix, Remove. It should finish the sentence “This commit will…”. Skip the full stop.

Try it

Judge each message. Swipe right if it is good, left if it needs work.

Swipe right for good, left for needs work. Or use the buttons.

1 / 8Add contact form

Watch

Many teams add a label in front. feat: is a new feature. fix: repairs a bug. docs: is for writing. This style is called Conventional Commits.

Check

You fixed a typo on the about page. Pick the best message.

Try it

Save about.html with a clean message.

Working folder

Staging area

Empty

Repository

3 save points
Add purple style
Add home page
Add README

You did it!

You can now write commit messages that make sense later.

Go deeper (optional)

More labels you will see: style:, refactor:, test: and chore:. Need more detail? Add a second -m for a longer body. Teams pick one language for messages. English is common, but Malay is fine too.

~/diary $ git add about.html~/diary $ git commit -m "feat: add about page" -m "It lists my favourite food."[main 8faee72] feat: add about page 1 file changed, 2 insertions(+) create mode 100644 about.html~/diary $ git log -n 1commit 8faee7295b0ed42b9665bc2e58c4068ef29c7d2e (HEAD -> main)Author: You <you@example.com>Date:   Fri Oct 30 09:04:00 2026 +0800    feat: add about page        It lists my favourite food.