Write better git commits
Last updated a year ago by ray725 .
MIT · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install bommit 
SYNC missed versions from official npm registry.


Write better git commits

oclif Version Downloads/week

bommit example


Standardizing git commits is difficult. It will be easier to write informative commits with a command-line tool that formats commit messages.

Commit Style

commit_type(affected_part): Summary here

commit_type is selected from a drop-down menu of ['feature', 'fix', 'docs', 'style', 'refactor', 'performance', 'test', 'build', 'revert']

affected_part is free text input; usually, it refers either to which core functionality it affects or which file it mainly impacts.

Summary is free text input; bommit enforces that it be concise.

In possible future versions, we may include different options for commit style.


Run npm i -g bommit


Stage all your files and run bommit. The equivalent command would be running git commit -am.

Alternatively, run bommit -a. The equivalent series commands would be git add -A then git commit -am.

Current Tags

  • 1.0.3                                ...           latest (a year ago)

4 Versions

  • 1.0.3                                ...           a year ago
  • 1.0.2                                ...           a year ago
  • 1.0.1                                ...           a year ago
  • 1.0.0                                ...           a year ago
Maintainers (1)
Today 0
This Week 0
This Month 0
Last Day 0
Last Week 0
Last Month 0
Dependencies (6)
Dev Dependencies (6)
Dependents (0)

Copyright 2014 - 2016 © |