Skip to content

[Feature]: Use commitlint hints for possible scopes #17

@alerque

Description

@alerque

Problem Statement

The current prompt leaves the commit scope pretty much up to chance.

Proposed Solution

Some existing Conventional Commits ecosystem tooling (including the commitlint project) use a meta data file to verify available scopes for a project. A quick check for this or similar known places to store scope lists could be checked and a list of allowed scopes could be added to the prompt.

For an example, see one of my projects: https://github.com/sile-typesetter/sile/blob/master/.commitlintrc.yml

Alternatives Considered

No response

Use Case

Commit messages would fit better in projects with strict rules for allowed scopes.

Additional Context

No response

Feature Scope

  • This fits within faff's core mission (AI commit message generation)
  • This would be a breaking change
  • This requires changes to external dependencies
  • This is a nice-to-have rather than essential

Checklist

  • I have searched existing issues to avoid duplicates
  • I have considered if this feature fits faff's scope

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions