commit-conventions

To generate conventional commit messages from changed files, this Skill analyzes your file paths and change intent to produce standardized output. It maps your edits to repository-specific scopes and formats them into the required lowercase <type>(<scope>): <description> structure automatically.

Scope inference in git version control automatically maps your changed file paths to the correct commit scope, such as core, tools, or cli. You need it when maintaining standardized commit histories across large repositories with strict formatting rules.

To format breaking changes in conventional commits, the Skill applies specific breaking-change notation alongside the required lowercase type and concise description. It ensures your commit message adheres to repository-specific rules for length limits and structural formatting without manual intervention.

Yes, you can use this for bug fix and documentation commits in your development workflow. The Skill supports feature work, tests, refactoring, and maintenance commits by applying OhMyCode commit rules to generate repository-compliant messages fast.

Yes, this Skill works without external dependencies or components. It internally applies the OhMyCode commit conventions to infer scopes from file paths and format your change intent into compliant conventional commit messages.