hermes-commit

You can enforce review gates and lint checks before committing by triggering the workflow after changes are reviewed. It requires a review pass, runs format and lint verification without auto-fixing, then plans and executes atomic commits with conventional messages.

Yes, the commit workflow supports both .NET and JavaScript/TypeScript projects. It automatically detects the project type to run the appropriate verify-no-changes or lint checks in verify-only mode before staging commits.

Automating conventional commit messages after review involves gathering staged changes, grouping them into small independent commits, and generating conventional messages. The workflow presents a commit plan for approval before executing the atomic commits individually.

The automated commit workflow stops when format or lint verification fails, or when a code review gate is not satisfied. It never alters source code to fix issues, instead halting the process and instructing you to fix the underlying problems first.

Yes, you can skip the code review gate when committing changes by using an explicit override option. This allows you to bypass the required review step and proceed directly to format verification and atomic commit planning.

To group staged changes into independent atomic commits, the workflow gathers all current changes and plans small, logical groupings. It generates conventional commit messages for each group and presents a complete commit plan before staging and executing them individually.