Commit Message

Generate conventional commit messages for DevFlow updates by applying type, scope, and subject formatting rules to changes across skills, agents, hooks, and docs. Scope is automatically derived from the touched area to ensure uniformity across commits.

The correct conventional commit message format is <type>(<scope>): <description>. Scope is derived from the touched DevFlow area, categorizing the change under skills, agents, hooks, or docs to maintain uniform commit histories.

Include a rationale in conventional commit messages by adding an optional body. This concise body explains non-trivial changes, providing necessary context for changelogs and code reviews during development and release workflows.

You need conventional commit messages for your development workflow when standardizing DevFlow changes across skills, agents, hooks, and docs. Standardized formatting makes commit histories significantly easier to review and revert.

Yes, you can use conventional commits for both development and release workflows. The standardized messages apply to commits across all DevFlow components, creating clear documentation suitable for pull requests and release notes.

Automating conventional commit messages is limited to DevFlow components like skills, agents, hooks, and docs. It enforces type, scope, and subject formatting but relies on the touched area to derive scope, requiring distinct component boundaries.