docs: => commitlint

Author: marionebl

Diff for: contributing.md

@@ -1,30 +1,28 @@
-> Lint commit messages against your conventional-changelog preset
+> Lint commit messages
 
-<p align="center">
-  <h1>conventional-changelog-lint</h1>
-</p>
+# commitlint
 
-Yeay! You want to contribute to conventional-changelog-lint. That's amazing!
+Yeay! You want to contribute to commitlint. That's amazing!
 To smoothen everyone's experience involved with the project please take note of the following guidelines and rules.
 
 ## Found an Issue?
-Thank you for reporting any issues you find. We do our best to test and make conventional-changelog-lint as solid as possible, but any reported issue is a real help.
+Thank you for reporting any issues you find. We do our best to test and make commitlint as solid as possible, but any reported issue is a real help.
 
-> conventional-changelog-lint issues
+> commitlint issues
 
 Please follow these guidelines when reporting issues:
 * Provide a title in the format of `<Error> when <Task>`
 * Tag your issue with the tag `bug`
 * Provide a short summary of what you are trying to do
 * Provide the log of the encountered error if applicable
-* Provide the exact version of conventional-changelog-lint. Check `npm ls conventional-changelog-lint` when in doubt
+* Provide the exact version of commitlint. Check `npm ls @commitlint/cli` when in doubt
 * Be awesome and consider contributing a [pull request](#want-to-contribute)
 
 ## Want to contribute?
-You consider contributing changes to conventional-changelog-lint – we dig that!
+You consider contributing changes to commitlint – we dig that!
 Please consider these guidelines when filing a pull request:
 
-> conventional-changelog-lint pull requests
+> commitlint pull requests
 
 * Follow the [Coding Rules](#coding-rules)
 * Follow the [Commit Rules](#commit-rules)
@@ -38,28 +36,22 @@ Please consider these guidelines when filing a pull request:
 	* What you removed
 
 ## Coding Rules
-To keep the code base of conventional-changelog-lint neat and tidy the following rules apply to every change
+To keep the code base of commitlint neat and tidy the following rules apply to every change
 
 > Coding standards
 
-* [Happiness](/sindresorhus/xo) enforced via eslint
+* [Happiness](/sindresorhus/xo) enforced
 * Favor micro library over swiss army knives (rimraf, ncp vs. fs-extra)
-* Coverage never drops below 90%
-* No change may lower coverage by more than 5%
 * Be awesome
 
 ## Commit Rules
-To help everyone with understanding the commit history of conventional-changelog-lint the following commit rules are enforced.
-To make your life easier conventional-changelog-lint is commitizen-friendly and provides the npm run-script `commit`.
+To help everyone with understanding the commit history of commitlint the following commit rules are enforced.
+To make your life easier commitlint is commitizen-friendly and provides the npm run-script `commit`.
 
 > Commit standards
 
-* [conventional-changelog](/commitizen/cz-conventional-changelog)
+* [conventional-changelog](./@commitlint/prompt)
 * husky commit message hook available
 * present tense
 * maximum of 100 characters
 * message format of `$type($scope): $message`
-
-
----
-Copyright 2016 by [Mario Nebl](https://github.com/marionebl) and [contributors](./graphs/contributors). Released under the [MIT license]('./license.md').