etherweave-commit-messages

Conventional commit messages enforce types like feat, fix, and refactor alongside a concise description. This format keeps your git history clean and readable, making code reviews significantly easier by clarifying the intent of each change.

Supported conventional commit scopes for EtherWeave development include gui, lib, cli, database, tools, docs, and tests. Scopes are appended to the commit type to specify the exact area of the codebase affected by the change.

Writing a pre-commit message for a feature branch involves crafting a cohesive, one-change-per-commit description. The Skill guides you to review staged changes and format them using conventional types and precise scopes before pushing to the repository.

Yes, you can use conventional commit types like chore, perf, docs, style, and test for repository updates. The Skill enforces these standard types alongside a concise description to categorize non-feature maintenance and improvements accurately.

Maintaining a clean git history for large codebases requires enforcing conventional commit formats with specific scopes. Using types like refactor and fix with area-specific scopes ensures precise tracking of changes across different modules like lib and cli.