Skip to content

[BUG] conventional_commits is too rigid #303

@dbasunag

Description

@dbasunag

Bug Description

Currently the assessment is based on presence of .commitlintrc.json or .husky https://github.com/ambient-code/agentready/blob/main/src/agentready/assessors/stub_assessors.py#L238

However, using .pre-commit-config.yaml for this purpose is common in pytest repos. e.g.

  - repo: https://github.com/espressif/conventional-precommit-linter
    rev: v1.11.0
    hooks:
      - id: conventional-precommit-linter
        stages: [ commit-msg ]
        args:
          - --types=build,ci,docs,feat,fix,perf,refactor,chore,test
          - --subject-min-length=10
          - --subject-max-length=80

would enforce some of the rules similar to .commitlintrc.json

To Reproduce

Steps to reproduce the behavior:

  1. Run agentready assess against a repo that enforces conventional commit message rules via .pre-commit-config.yaml and see that conventional_commits check fails:
conventional_commits                ❌ FAIL         not configured (need: configured)

Expected Behavior

This check should be expanded to consider .pre-commit-config.yaml

Actual Behavior

conventional_commits check fails

Environment

  • OS: macOS 26.2
  • Version: [e.g. 1.0.0]
  • Python Version: 3.14

Additional Context

Add any other context about the problem here. Include screenshots if applicable.

Possible Solution

If you have suggestions on how to fix the bug, please describe them here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions