@fatso83/check-commit-msg
Advanced tools
Check if your commit message follows Chris Beam's "Seven rules of a good commit message"
Simple util to check that commits follow a certain template
1. Separate subject from body with a blank line
2. Limit the subject line to 50 characters
3. Capitalize the subject line
4. Do not end the subject line with a period
5. Use the imperative mood in the subject line
6. Wrap the body at 72 characters
7. Use the body to explain what and why vs. how
Currently it also checks if your commit starts with a JIRA identifier (FOO-123) as well, but this is easy to fix/remove.
npm install -g @fatso83/check-commit-msg
echo << 'EOF' > .git/hooks/commit-msg
check-commit-msg $1
EOF
chmod +x .git/hooks/commit-msg #make it executable
If you use husky in your NPM commit hooks
npm install -D @fatso83/check-commit-msg
Then add this to your package.json scripts' section:
"commitmsg": "node -r '@fatso83/check-commit-msg/husky'"
Need something? Suggestions? Pull requests welcome :)
FAQs
Check if your commit message follows Chris Beam's "Seven rules of a good commit message"
We found that @fatso83/check-commit-msg demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.