chore: Add commit hooks for testing and linting (#149)

chore: Add commit hooks for testing and linting

Author: bahrmichael

Diff for: .husky/pre-commit

@@ -0,0 +1,4 @@
+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
+npm run lerna-lint

Diff for: .husky/pre-push

@@ -0,0 +1,4 @@
+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
+npm run test

Diff for: CONTRIBUTING.md

@@ -28,23 +28,24 @@ Contributions via pull requests are much appreciated. Before sending us a pull r
 1. You are working against the latest source on the **main** branch.
 2. You check existing open, and recently merged pull requests to make sure someone else hasn't addressed the problem already.
 3. You open an [RFC issue](https://github.com/awslabs/aws-lambda-powertools-typescript/issues/new?assignees=&labels=RFC%2C+triage&template=rfc.md&title=RFC%3A+) to discuss any significant work - we would hate for your time to be wasted.
+4. You lint and test the code. When you've setup the repository with `npm run init-environment`, pre-commit and push-hooks will automatically lint and test the code. Pull request builds will run the same checks as well.
 
 ### Dev setup
 
 To send us a pull request, please follow these steps:
 
 1. Fork the repository.
 2. Install dependencies: `npm install`
-3. Create a new branch to focus on the specific change you are contributing e.g. `git checkout -b improv/logger-debug-sampling`
-4. Run all tests, and code baseline checks: `npm run test`
-5. Commit to your fork using clear commit messages.
-6. Send us a pull request with a [conventional semantic title](https://github.com/awslabs/aws-lambda-powertools-typescript/pull/67), and answering any default questions in the pull request interface.
-7. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
-
-GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
+3. Prepare utilities like commit hooks: `npm run init-environment`
+4. Create a new branch to focus on the specific change you are contributing e.g. `git checkout -b improv/logger-debug-sampling`
+5. Run all tests, and code baseline checks: `npm run test`
+6. Commit to your fork using clear commit messages.
+7. Send us a pull request with a [conventional semantic title](https://github.com/awslabs/aws-lambda-powertools-typescript/blob/main/.github/semantic.yml), and answering any default questions in the pull request interface. [Here's an example](https://github.com/awslabs/aws-lambda-powertools-python/pull/67).
+8. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
+
+GitHub provides an additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
 [creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
 
-
 ### Conventions
 
 Category | Convention

Diff for: npm-shrinkwrap.json

@@ -5,6 +5,8 @@
   "main": "lib/index.js",
   "types": "lib/",
   "scripts": {
+    "init-environment": "husky install",
+    "test": "npm run lerna-test",
     "commit": "commit",
     "lerna-ci": "lerna exec -- npm ci",
     "lerna-test": "lerna exec -- npm run test",
@@ -39,6 +41,7 @@
     "@typescript-eslint/eslint-plugin": "^4.11.1",
     "@typescript-eslint/parser": "^4.11.1",
     "eslint": "^7.16.0",
+    "husky": "^7.0.1",
     "jest": "^27.0.4",
     "lerna": "^4.0.0",
     "ts-jest": "^27.0.3",