Learn the vocabulary of structured commit prefixes that a tool can parse to automate releases.
0 / 5 completed
1 / 5
At standup, a dev mentions writing every commit message with a structured prefix, like feat:, fix:, or chore:, specifically so a tool can parse that prefix later to automatically determine the next version bump and generate a changelog. What is this commit message convention called?
Conventional commits is exactly this: it is a commit message convention with a structured prefix, such as feat:, fix:, or chore:, that a tool can parse to automatically determine the next semantic version bump and generate a changelog, without a human having to manually track or summarize every change. A hash collision is an unrelated hash-table concept about two keys sharing a bucket. This structured-prefix-a-tool-can-parse approach is exactly why conventional commits enable automated versioning and changelog generation.
2 / 5
During a design review, the team adopts conventional commits and wires up a release tool that reads each commit's feat:, fix:, or chore: prefix, specifically because the tool can now determine automatically whether the next release needs a minor or patch version bump. Which capability does this provide?
Conventional commits here provide automated version bumping and changelog generation from commit history, since a tool can parse each commit's structured prefix to determine the correct version bump and compile a changelog, instead of a person manually reviewing every commit to decide. Writing commit messages with no structured prefix at all gives a release tool no reliable signal to parse, forcing a human to review commit history and decide the version bump manually every time. This tool-parses-the-structured-prefix behavior is exactly why conventional commits are adopted alongside automated release tooling.
3 / 5
In a code review, a dev notices commit messages across the project are written in free-form prose with no structured prefix at all, meaning the team's release tool has nothing to parse and a person has to manually read through commit history before every release to decide the version bump. What does this represent?
This is a missed opportunity to adopt conventional commits, since a structured feat:/fix:/chore: prefix would let the release tool determine the version bump and changelog automatically instead of requiring a manual review of commit history. A cache eviction policy is an unrelated concept about discarded cache entries. This free-form-commit-messages-with-nothing-to-parse pattern is exactly the kind of manual-toil gap a reviewer flags once a release tool is expected to automate versioning.
4 / 5
An incident report shows a release shipped with the wrong version bump, because commit messages were written in free-form prose with no structured prefix, and the person manually reviewing commit history before the release misjudged whether a change was a breaking feature or a minor fix. What practice would prevent this?
Adopting conventional commits with a structured feat:/fix:/chore: prefix lets the release tool determine the version bump automatically and consistently from commit history instead of relying on a person's manual judgment. Continuing to write commit messages in free-form prose with no structured prefix regardless of how often a manual review of commit history misjudges the correct version bump is exactly what caused the wrong version bump described in this incident. This adopt-a-structured-prefix approach is the standard fix once manual version-bump judgment is confirmed to be error-prone.
5 / 5
During a PR review, a teammate asks why the team adopts conventional commits with a structured prefix instead of simply asking every developer to write a clear, descriptive commit message in their own words. What is the reasoning?
A structured prefix like feat: or fix: gives a release tool a reliable, machine-parseable signal to automate version bumps and changelog generation, while a clear, descriptive commit message in a developer's own words is valuable for humans to read but gives a tool no consistent, parseable signal to automate anything from unless someone manually reads and classifies every commit. This is exactly why conventional commits underpin automated release tooling, while free-form descriptive messages remain a separate, human-facing concern.
What does the "Conventional Commits Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to conventional commits vocabulary through 5 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 5 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — this module shares real-world context with 9 other vocabulary modules. See "Related vocabulary" below to keep building a connected skill set.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.