message: docs(contributing): add details to "Steps to PR"
diff: @@ -161,17 +161,25 @@ https://www.conventionalcommits.org/ or check out the
  ### Steps to PR
  -- Fork of the chakra-ui repository and clone your fork
  -- Create a new branch out of the `develop` branch. We follow the convention
  - `[type/scope]`. For example `fix/accordion-hook`, `docs/menu-typo`
  +1. Fork of the chakra-ui repository and clone your fork
  - - `type` can be either `docs`, `fix`, `feat`, `build`, or any other
  - conventional commit type
  - - `scope` is just a short id that describes the scope of work.
  +2. Create a new branch out of the `develop` branch. We follow the convention
  + `[type/scope]`. For example `fix/accordion-hook` or `docs/menu-typo`. `type`
  + can be either `docs`, `fix`, `feat`, `build`, or any other conventional
  + commit type. `scope` is just a short id that describes the scope of work.
  -- Run `yarn changeset` to create a detailed description of your changes. This
  +3. Make and commit your changes following the
  + [commit convention](https://github.com/chakra-ui/chakra-ui/blob/develop/CONTRIBUTING.md#commit-convention).
  + As you develop, you can run `yarn pkg <module> build` and
  + `yarn pkg <module> test` to make sure everything works as expected. Please
  + note that you might have to run `yarn boot` first in order to build all
  + dependencies.
  +
  +4. Run `yarn changeset` to create a detailed description of your changes. This
  will be used to generate a changelog when we publish an update.
  - [Learn more about Changeset](https://github.com/atlassian/changesets/tree/master/packages/cli)
  + [Learn more about Changeset](https://github.com/atlassian/changesets/tree/master/packages/cli).
  + Please note that you might have to run `git fetch origin master:master`
  + (where origin will be your fork on GitHub) before `yarn changeset` works.
  > If you made minor changes like CI config, prettier, etc, you can run
  > `yarn changeset add --empty` to generate an empty changeset file to document
  