chore(commitizen): migrate to 'pre-commit-crocodile' 2.0.1

      ## Conventional Commits - Customized specification

      The commit contains the following structural elements, to communicate

      intent to the consumers of your library:

      The commit contains the following structural elements:

      ### Commit type

      fix: a commit of the type fix patches a bug in your codebase

      (this correlates with PATCH in semantic versioning).

      feat: a commit of the type feat introduces a new feature to the codebase

      (this correlates with MINOR in semantic versioning).

      Others: commit types other than fix: and feat: are allowed,

      like chore:, docs:, style:, refactor:, perf:, test:, and others.

      We also recommend improvement for commits that improve a current

      implementation without adding a new feature or fixing a bug.

      For temporary commits, start with 'wip' or 'WIP' to ignore commit validation.

      - fix: Bug or issues fixes

      - feat: New or extended feature

      - chore: Changes to non-production code

      - docs: Documentation only changes

      - style: Cosmetic changes only (white-space, formatting, etc)

      - refactor: Code changes that neither fix a bug nor add a feature

      - perf: Code change that improve performance

      - security: Changes resolve security related issues

      - test: Adding missing or correcting existing tests

      - build: Changes to the build system or dependencies (example: makefile, pip, docker)

      - ci: Changes to CI configuration files and scripts (example: gitlab-ci)

      - improvement: Changes that improve sources without any impact

      - wip: Temporary commits meant for local developments and rebases

      ### Commit scope

      A scope has to be provided to a commit’s type, to provide additional contextual information,

      such as the changed file, the containing folder or a globally modified feature,

      and is contained within parenthesis, e.g., feat(parser): add ability to parse arrays.

      and is contained within parenthesis, e.g. feat(parser): add ability to parse arrays.

      ### Commit breaking changes

      BREAKING CHANGE: A commit with '!' before the ':' or that has the text BREAKING CHANGE:

      at the beginning of its optional body or footer section introduces a breaking API change

      (correlating with MAJOR in semantic versioning).

      A BREAKING CHANGE can be part of commits of any type.

      ### Commit syntax

            name: 'test: Adding missing or correcting existing tests'

            key: t

          - value: build

            name: 'build: Changes to the build system or dependencies _(example: makefile, pip, docker)'

            name: 'build: Changes to the build system or dependencies (example: makefile, pip, docker)'

            key: b

          - value: ci

            name: 'ci: Changes to CI configuration files and scripts (example: gitlab-ci)'

  # Repository: pre-commit-crocodile

  - repo: https://gitlab.com/RadianDevCore/tools/pre-commit-crocodile

    rev: 2.0.0

    rev: 2.0.1

    hooks:

      - id: prepare-commit-message