fix: remove yarn commit requirement

Author: Evgeny Zakharov

README.md

@@ -124,7 +124,7 @@ Then, the `release` workflow handles everything:
 ### Regular flow
 
 1. Create [feature branch](#conventions)
-2. Make changes in your feature branch and [commit](#conventions) using `yarn commit`
+2. Make changes in your feature branch and [commit](#conventions)
 3. Create a Pull Request from your feature branch to `main`  
    The PR is needed to test the code before pushing to release branch
 4. If your PR contains breaking changes, don't forget to put a `BREAKING CHANGES` label
@@ -136,7 +136,7 @@ Then, the `release` workflow handles everything:
 1. Assume your prerelease tag is `beta`
 2. Create `release/beta` branch
 3. Create [feature branch](#conventions)
-4. Make changes in your feature branch and [commit](#conventions) using `yarn commit`
+4. Make changes in your feature branch and [commit](#conventions)
 5. Create a Pull Request from your feature branch to `release/beta`  
    The PR is needed to test the code before pushing to release branch
 6. Create Github release with tag like `v1.0.0-beta`, pointing to `release/beta` branch  
@@ -153,8 +153,8 @@ Then, the `release` workflow handles everything:
 
 **Commits**:
 
-- Should be created using `yarn commit` command
 - Should follow the [Conventional Commits specification](https://www.conventionalcommits.org)
+- You can find supported types and scopes into `.cz-config.js`
 
 **Pull requests**:
 

package.json

@@ -22,7 +22,6 @@
     "test:watch": "yarn test --watchAll",
     "lint": "eslint --ext .ts,.tsx src",
     "lint:fix": "yarn lint --fix",
-    "commit": "cz",
     "prepare": "is-ci || husky install",
     "postinstall": "yarn prepare",
     "prepack": "pinst --disable",