Commitlint
Last updated: Oct 28, 2026
Rationale
Commitlint is the tool that Fluid Attacks uses to standardize its commit messages and to enforce compliance during CI/CD tests. With Commitlint, the commit messages of Fluid Attacks have a good structure:
- They follow a convention.
- Humans and machines can read them.
These are the primary reasons why Fluid Attacks selected it:
- It gives Fluid Attacks a standardized commit history, not a messy one. This history shows much more clearly, at a high level, what each commit does.
- It can test commit messages through a CLI. Thus, Fluid Attacks can run it automatically as a CI job.
- Because the commit data is standardized, Fluid Attacks can run data analytics on its commit history. For example, it can answer questions like "What percentage of the commits in the last month were backend features?" and "How many developers worked on the front end of our application in the last month?"
- It is open source.
- A large community uses it.
- With it, Fluid Attacks can declare its own syntax.
- It supports many rules that Fluid Attacks can adjust as necessary.
Alternatives
git-commit-msg-linter: It has a much smaller ruleset. A smaller community uses it.
Usage
Fluid Attacks uses Commitlint to lint the commit messages in its repository.