validate-commit-msg: enforce types/scopes/refs by default

[gerchowl]

cc @c-vigo

Suggestion: validate-commit-msg should ship with types, scopes, and refs enforced by default (strict-by-default) instead of being opt-in via commented-out CLI args.

Why: Users won't discover commented-out config. If enforcement is on by default, they experience the value immediately. The pre-commit error message can link to .pre-commit-config.yaml with a "customize or disable" hint — easy opt-out beats invisible opt-in.

TL;DR: Default strict → show config path in error → users discover greatness, can relax if needed.

Ref: .pre-commit-config.yaml lines 120–126.

[c-vigo]

I agree on enforced types, but not so much on scopes since they can be very project-dependent, and there is even a question to be made whether they are useful or not.

Currently we use:

  # Commit message validation (commit-msg stage)
  - repo: local
    hooks:
      - id: validate-commit-msg
        name: validate commit message
        entry: uv run validate-commit-msg
        language: system
        stages: [commit-msg]
        args: [
          "--types", "feat,fix,docs,chore,refactor,test,ci,build,revert,style",
          "--scopes", "setup,image,vigutils",
          "--refs-optional-types", "chore",
        ]

[gerchowl]

I'd say so, i.e. for changelog generation/grouping and, yes, scopes one could do some generic (or even have them auto populated based on codebase/project analysis / AST .. :-D)