docs(README): adjust README

Author: nivekcode

README.md

@@ -0,0 +1,31 @@
+# node-command-line-starter
+Progammers are lazy. As soon as we have to do the same task over and over again we start on automizing it.
+Automization is often done in the form of a command line utility.
+
+This starter provides you with all the necessary setup to quickly create your node-command-line utility. It provides you all the
+necessary setup so that you can focus on your util and don't loose time with
+the project setup.
+
+The starter also provides you all the setup for quickly pushing new versions to your npm repositiory.
+
+## What's included?
+
+### Testing
+- [Jest](https://jestjs.io/) - JavaScript Testing Framework
+- Jest configurations to mock third party libaries
+- Sample tests
+
+### Command line utils
+- [Commander](https://github.com/tj/commander.js) - Complete solution for node.js command-line interfaces.
+- [Chalk](https://github.com/chalk/chalk) - Terminal string styling
+- [Boxen](https://github.com/sindresorhus/boxen#readme) - Create boxes in terminal
+
+### Dev utilities
+- [Prettier](https://prettier.io/) - Code formater
+- [Husky](https://github.com/typicode/husky) and [Lint-staged](https://github.com/okonet/lint-staged) to run prettier on each commit on staged files.
+
+### Build tools
+- [Codecov](https://codecov.io/) - Integration to upload your coverage report to codecov
+- [Travis](https://travis-ci.org/) - Sample travis file with all the necessary build steps
+- [SemanticRelease](https://github.com/semantic-release/semantic-release) - All the setup to use semantic release. Publish your command line utility to npm by using conventional commits
+