commit

Auto-generating git commit messages from code changes involves analyzing your staged files and applying a deterministic format. This skill reads your provided changes and optional feature name to produce a compliant message automatically.

Linking git commits to requirements is done by reading a spec.md file to map your code changes to specific REQ numbers. This ensures every generated commit message references the relevant feature spec for clear traceability.

Enforcing a consistent commit convention across your repository is achieved by applying a deterministic message format to every change. This skill analyzes your code modifications and generates messages that align with your project's defined conventions.

Mapping code changes to feature specs for code review requires referencing specific REQ numbers in your commit history. This skill automatically analyzes changes and generates commits with messages that reference your spec.md requirements.

You do not strictly need a spec.md file to generate commit messages, but providing one is required to link changes to requirements and include REQ numbers. You can simply provide the code changes and an optional feature name to generate a compliant message.