## Description ## Motivation and Context ## Usage examples ```js // commitlint.config.js module.exports = {}; ``` ```sh echo "your commit message here" | commitlint # fails/passes ``` ## How Has This Been Tested? ## Types of changes - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) ## Checklist: - [ ] My change requires a change to the documentation. - [ ] I have updated the documentation accordingly. - [ ] I have verified that any documentation examples I added/changed actually work. - [ ] I have added tests to cover my changes. - [ ] All new and existing tests passed. - [ ] For a feature/bug fix, my commits follow the [test-driven flow](https://github.com/conventional-changelog/commitlint/blob/master/.github/CONTRIBUTING.md#test-driven-development): a failing-test commit, then the implementation.