Add lenient commit message linter with commitlint

[Jerek0]

Add lenient commit message linter with commitlint

This PR introduces a lightweight and opinionated commitlint setup. The goal is to gently encourage more descriptive and meaningful commit messages, without enforcing strict Conventional Commits or requiring type prefixes like feat: or fix:.

🧠 Why?

Commit messages are an essential part of project history. By enforcing a few light rules, we can:

• Improve readability in tools like git log, GitHub, and Git clients
• Encourage better collaboration and long-term project understanding
• Avoid throwaway commits like wip, qa, or fix that lack context

This linter is here to help, not get in the way.

🔧 What it enforces

Rule	Description
✅ subject is required	No empty messages allowed
✅ Minimum 3 words	Avoids vague one-word messages
✅ Length between 5–100 chars	Enough space to be clear, but concise
🚫 No trailing period	Keeps subject lines short and to the point
🆗 Body is optional	If present, must start with a blank line and wrap lines at 120 characters

Tip

If 100 characters isn’t enough to describe your change, keep the subject short and clear, then use the commit body to provide additional context/information.

🛠️ How it works

1. When running git commit, a commit-msg hook triggers commitlint on the last commit message
2. The message is validated against our config
3. If the message fails any error-level rules, the commit is blocked with an explanation. Otherwise, it silently goes through as usual

This is powered by simple-git-hooks, which runs commitlint automatically at commit time.

Example

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
astro-boilerplate	✅ Ready (Inspect)	Visit Preview	Jul 3, 2025 5:49pm

[devenini]

Possible to convert commitlint.config.js to TypeScript (.ts) so it’s consistent with the other JavaScript files in the repo?