git-commit

To generate conventional commit messages for documentation changes, use this Skill to automatically format your commits with the standard `type(scope): subject` structure. It enforces specific guidelines for documenting changes within the `docs/` and `reports/` directories.

The correct commit format for diopside workflow updates follows the Japanese Conventional Commits specification. This Skill enforces a structured message including a specific type, scope, and subject to ensure a consistent and discoverable project history.

When updating a requirement document in `docs/`, this Skill helps you formulate a structured commit message like `docs(RQ-SC-001): Update stakeholder definition`. It applies specific type and scope guidelines for the diopside documentation directories.

Yes, you can use conventional commits for changes in the `reports/` and `skills/` directories. This Skill provides specific guidelines for determining the appropriate type and scope when committing changes related to these diopside operational workflows.

The limitation of this automated conventional commit generation is its specialization for the diopside context. It specifically enforces structured Japanese commit messages for documentation and operational changes within the `docs/`, `reports/`, and `skills/` directories.