Understanding: usage with commitlint

I am already using commitlint with conventional commits in my project to lint my commit messages as part of husky commit-msg githook.

I also want to have the ability to prompt users for correctly format messages while they are committing instead of checking before the actual commit, which commitlint enables with commitlint prompt Ofcourse, commitizen enables this as well with

"config": {
    "commitizen": {
      "path": "path/to/adapter"
    }
  },

Is there any benefit of using commitizen if I am using commitlint already?

Or, would it make sense to only use commitizen?

Does commitizen provide a commit-msg hook? as i would like to still lint my git commit messages if a user does not follow the prompt that commitizen provides for commit.

Assuming I do get some benefits by using both commitizen and commitlint, would it be better for me to use the commitlint adapter with config-conventional or cz-conventional-changelog?

[gaurav5430]

@castarco I don’t have any issues with making the setup work with cz-conventional-changelog and commitlint with husky, my question is more to understand whether I should be using cz-conventional-changelog at all if I am already using commitlint, should I just use the commitlint adapter instead of cz-conventional-changelog? And further, should I even use commitizen at all if I am already using commitlint? Can I not just use the commitlint prompt to setup a commit script same as git-cz, is there a benefit one approach provides over the other?

[Axedyson]

How does cz-conventional-changelog use the commitlint config?

I would like to know that too